Cyber Resilience

CVE-2025-49113

RCE in Roundcube Webmail ≤ 1.5.10

CISA KEVActive ExploitationEUVD ExploitedPublic PoCRCEDeserialization
Published
02 June 2025
Modified
17 June 2026
KEV Added
20 February 2026
Patch / advisory
CVSS Score v3.1 9.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.98 99.9th percentile
Risk Priority 94 floored blend · peak EPSS

Summary

CVE-2025-49113 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Roundcube Webmail. Its CVSS base score is 9.9 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Roundcube Webmail before version 1.5.10 and 1.6.x before 1.6.11 contains a deserialization flaw in program/actions/settings/upload.php where the _from URL parameter is not validated, allowing PHP object injection that leads to remote code execution. The issue is tracked as CWE-502 and carries a CVSS 3.1 score of 9.9 reflecting network-accessible attack with low complexity and high impact across confidentiality, integrity, and availability.

Authenticated users can supply a crafted _from parameter to trigger the deserialization and execute arbitrary code on the server. Because the vector requires only a valid account and no user interaction, the flaw enables straightforward post-authentication compromise of affected installations.

Public commits and the associated pull request on the Roundcube repository show that the maintainers addressed the input validation gap in the fixed releases; administrators should upgrade to 1.5.10 or 1.6.11 and verify that the patched upload.php is deployed. The EPSS score has reached a peak of 0.9211 with a current value of 0.9047, indicating sustained exploitation interest after disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Roundcube Webmail before 1.5.10 and 1.6.x before 1.6.11 allows remote code execution by authenticated users because the _from parameter in a URL is not validated in program/actions/settings/upload.php, leading to PHP Object Deserialization.

CWE(s)
KEV Date Added
20 February 2026

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-37383Same product: Debian Debian Linuxboth on KEV
CVE-2023-43770Same product: Debian Debian Linuxboth on KEV
CVE-2017-16651Same product: Debian Debian Linuxboth on KEV
CVE-2026-35537Same product: Roundcube Webmail
CVE-2021-44026Same product: Debian Debian Linuxboth on KEV
CVE-2024-37384Same product: Debian Debian Linux
CVE-2023-5631Same product: Debian Debian Linuxboth on KEV
CVE-2020-13965Same product: Debian Debian Linuxboth on KEV
CVE-2020-35730Same product: Debian Debian Linuxboth on KEV
CVE-2020-17144Same product class: email / collaborationboth on KEV

Affected Assets

roundcube
webmail
≤ 1.5.10 · 1.6.0 — 1.6.11
debian
debian linux
11.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can uncover deserialization flaws before deployment.

Input validation directly stops deserialization of untrusted data by ensuring inputs are valid before processing.

Engineering principles such as safe deserialization and input sanitization structurally prevent the weakness from being introduced.

Integrity verification tools can detect malformed or tampered serialized data after the fact.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 none match
prevents

PR.PS-02 addresses only post-deployment updates/patching and cannot prevent introduction of unsafe deserialization code, yet it can remediate some instances when the flaw exists in outdated libraries or components.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing includes validation of deserialization routines and the use of untrusted data, reducing the likelihood that unsafe object reconstruction will be deployed.

prevents

Requiring vetted libraries, regular updates and SAST before release reduces the likelihood that deserialization logic will accept and act on attacker-controlled serialized objects.

finds

Regular scanning of third-party libraries and timely patching reduce the likelihood that unsafe deserialization vulnerabilities remain active.

none

Mandatory malware scanning of data received over networks or storage media intercepts malicious serialized payloads before they are deserialized by the target application.

References