CVE-2025-49113
KEVRoundCube Webmail Deserialization of Untrusted Data Vulnerability
Description
RoundCube Webmail contains a deserialization of untrusted data vulnerability that allows remote code execution by authenticated users because the _from parameter in a URL is not validated in program/actions/settings/upload.php.
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.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HPublishedJun 2, 2025
Last modifiedJun 17, 2026
Added to KEVFeb 20, 2026
Remediation dueMar 13, 2026
References
- fearsoff.org/research/roundcubeThird Party Advisory
- github.com/roundcube/roundcubemail/commit/0376f69e958a8fef7f6f09e352c541b4e7729c4dPatch
- github.com/roundcube/roundcubemail/commit/7408f31379666124a39f9cb1018f62bc5e2dc695Patch
- github.com/roundcube/roundcubemail/commit/c50a07d88ca38f018a0f4a0b008e9a1deb32637ePatch
- github.com/roundcube/roundcubemail/pull/9865Issue Tracking
- github.com/roundcube/roundcubemail/releases/tag/1.5.10Release Notes
- github.com/roundcube/roundcubemail/releases/tag/1.6.11Release Notes
- roundcube.net/news/2025/06/01/security-updates-1.6.11-and-1.5.10Vendor Advisory
- vicarius.io/vsociety/posts/cve-2025-49113-roundcube-mitigation-scriptExploitMitigation
- vicarius.io/vsociety/posts/cve-2025-49113-roundcube-vulnerability-detectionExploitMitigation
- openwall.com/lists/oss-security/2025/06/02/3Mailing ListThird Party Advisory
- lists.debian.org/debian-lts-announce/2025/06/msg00008.htmlMailing ListThird Party Advisory
0 recent articles mention this CVE
89
Risk assessment · Critical
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 227 days
- CVSS
- 9.9 CRITICAL
- EPSS (30-day exploit probability)
- 99.7% · top 1% of all CVEs
- Weakness
- CWE-502
- Attack vector
- Network, remotely reachable
Recommended actions
- 1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.