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.
CVE-2025-49113
Score elevated to 9.9 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-02-20), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.9 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 9.9
- EG Score
- 9.9(high)
- EG Risk
- 85(Attend)EG Risk 85/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity99% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 99%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
June 2, 2025
Last Modified
February 23, 2026
Advisory Details (10)
Auto-updated Sep 14, 2026CVE-2025-49113 Roundcube Vulnerability Detection - vsociety
https://www.vicarius.io/vsociety/posts/cve-2025-49113-roundcube-vulnerability-detectionCVE-2025-49113 Roundcube Mitigation Script - vsociety
https://www.vicarius.io/vsociety/posts/cve-2025-49113-roundcube-mitigation-scriptSecurity updates 1.6.11 and 1.5.10 released
https://roundcube.net/news/2025/06/01/security-updates-1.6.11-and-1.5.10Roundcube Webmail 1.6.11
Patch available: roundcube/roundcubemail 1.6.11
https://github.com/roundcube/roundcubemail/releases/tag/1.6.11Roundcube Webmail 1.5.10
Patch available: roundcube/roundcubemail 1.5.10
https://github.com/roundcube/roundcubemail/releases/tag/1.5.10Validate URL parameter in upload code
Fix merged in roundcube/roundcubemail PR #9865 on 2025-06-01 — awaiting tagged release
https://github.com/roundcube/roundcubemail/pull/9865commit c50a07d88ca3 (roundcube/roundcubemail)
Fix landed in roundcube/roundcubemail commit c50a07d88ca3 — awaiting tagged release
https://github.com/roundcube/roundcubemail/commit/c50a07d88ca38f018a0f4a0b008e9a1deb32637ecommit 7408f3137966 (roundcube/roundcubemail)
Fix landed in roundcube/roundcubemail commit 7408f3137966 — awaiting tagged release
https://github.com/roundcube/roundcubemail/commit/7408f31379666124a39f9cb1018f62bc5e2dc695commit 0376f69e958a (roundcube/roundcubemail)
Fix landed in roundcube/roundcubemail commit 0376f69e958a — awaiting tagged release
https://github.com/roundcube/roundcubemail/commit/0376f69e958a8fef7f6f09e352c541b4e7729c4dRoundcube ≤ 1.6.10 Post-Auth RCE via PHP Object Deserialization [CVE-2025-49113]
https://fearsoff.org/research/roundcubePatch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | roundcube-sqlite3 (1.6.6+dfsg-2ubuntu0.1) @ noble | 2026-09-19 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| roundcube | 1.4.11+dfsg.1-4 ... 1.4.15+dfsg.1-1~deb11u2~bpo10+1 (13 versions) | 1.4.15+dfsg.1-1+deb11u5 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| roundcube | 1.6.1+dfsg-1 ... 1.6.5+dfsg-1~deb12u1 (12 versions) | 1.6.5+dfsg-1+deb12u5 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| roundcube | — | 1.6.11+dfsg-1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| roundcube | — | 1.6.11+dfsg-1 | — |
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| roundcube/roundcubemail | — | 1.6.11 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 49× in last 7d / 193× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 659 total refreshes for this CVE.
- 2026-09-19 06:35 UTCVendor advisory
- 2026-09-19 02:56 UTCVendor advisory
- 2026-09-18 23:17 UTCVendor advisory
- 2026-09-18 19:38 UTCVendor advisory
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 12:17 UTCVendor advisory
- 2026-09-18 08:38 UTCVendor advisory
- 2026-09-18 04:59 UTCVendor advisory
- 2026-09-18 01:20 UTCVendor advisory
- 2026-09-17 21:41 UTCVendor advisory
- 2026-09-17 18:01 UTCVendor advisory
- 2026-09-17 14:22 UTCVendor advisory
- 2026-09-17 10:42 UTCVendor advisory
- 2026-09-17 07:03 UTCVendor advisory
- 2026-09-17 03:24 UTCVendor advisory
- 2026-09-16 23:45 UTCVendor advisory
- 2026-09-16 20:05 UTCVendor advisory
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 12:46 UTCVendor advisory
- 2026-09-16 09:07 UTCVendor advisory
- 2026-09-16 05:27 UTCEG score recompute
- 2026-09-16 05:27 UTCVendor advisory
- 2026-09-16 01:48 UTCVendor advisory
- 2026-09-15 22:09 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-15 18:30 UTCVendor advisory
- 2026-09-15 14:51 UTCVendor advisory
- 2026-09-15 11:12 UTCVendor advisory
- 2026-09-15 07:32 UTCVendor advisory
- 2026-09-15 03:53 UTCVendor advisory
- 2026-09-15 00:14 UTCVendor advisory
- 2026-09-14 20:35 UTCVendor advisory
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 16:56 UTCVendor advisory
- 2026-09-14 13:17 UTCVendor advisory
- 2026-09-14 09:38 UTCVendor advisory
- 2026-09-14 05:59 UTCVendor advisory
- 2026-09-14 02:20 UTCVendor advisory
- 2026-09-13 22:41 UTCVendor advisory
- 2026-09-13 19:02 UTCVendor advisory
- 2026-09-13 15:23 UTCVendor advisory
- 2026-09-13 11:44 UTCVendor advisory
- 2026-09-13 08:04 UTCVendor advisory
- 2026-09-13 04:26 UTCVendor advisory
- 2026-09-13 00:47 UTCVendor advisory
- 2026-09-12 21:08 UTCVendor advisory
- 2026-09-12 17:28 UTCVendor advisory
- 2026-09-12 13:49 UTCVendor advisory
- 2026-09-12 10:10 UTCVendor advisory
- 2026-09-12 06:31 UTCVendor advisory
- 2026-09-12 02:52 UTCVendor advisory
- 2026-09-11 23:12 UTCVendor advisory
- 2026-09-11 19:33 UTCVendor advisory
- 2026-09-11 18:49 UTCCISA KEV update
- 2026-09-11 15:54 UTCVendor advisory
- 2026-09-11 12:15 UTCVendor advisory
- 2026-09-11 08:35 UTCVendor advisory
- 2026-09-11 04:56 UTCVendor advisory
- 2026-09-11 01:17 UTCVendor advisory
- 2026-09-10 21:38 UTCVendor advisory
- 2026-09-10 19:28 UTCCISA KEV update
- 2026-09-10 17:59 UTCVendor advisory
- 2026-09-10 10:39 UTCVendor advisory
- 2026-09-10 06:58 UTCVendor advisory
- 2026-09-10 03:19 UTCVendor advisory
- 2026-09-09 23:40 UTCVendor advisory
- 2026-09-09 20:00 UTCVendor advisory
- 2026-09-09 19:08 UTCCISA KEV update
- 2026-09-09 12:41 UTCVendor advisory
- 2026-09-09 09:02 UTCVendor advisory
- 2026-09-09 05:22 UTCVendor advisory
- 2026-09-09 01:44 UTCVendor advisory
- 2026-09-08 22:04 UTCEG score recompute
- 2026-09-08 22:04 UTCVendor advisory
- 2026-09-08 21:59 UTCEPSS rescore
- 2026-09-08 18:54 UTCCISA KEV update
- 2026-09-08 18:25 UTCVendor advisory
- 2026-09-08 14:46 UTCVendor advisory
- 2026-09-08 11:05 UTCVendor advisory
- 2026-09-08 07:24 UTCVendor advisory
- 2026-09-08 03:45 UTCVendor advisory
- 2026-09-08 00:06 UTCVendor advisory
- 2026-09-07 20:26 UTCVendor advisory
- 2026-09-07 16:47 UTCEG score recompute
- 2026-09-07 16:47 UTCVendor advisory
- 2026-09-07 16:00 UTCEPSS rescore
- 2026-09-07 16:00 UTCEPSS rescore
- 2026-09-07 09:28 UTCVendor advisory
- 2026-09-07 05:46 UTCVendor advisory
- 2026-09-06 22:26 UTCVendor advisory
- 2026-09-06 18:47 UTCVendor advisory
- 2026-09-06 15:07 UTCVendor advisory
- 2026-09-06 11:26 UTCVendor advisory
- 2026-09-06 07:47 UTCVendor advisory
- 2026-09-06 04:08 UTCVendor advisory
- 2026-09-06 00:29 UTCVendor advisory
- 2026-09-05 20:49 UTCVendor advisory
- 2026-09-05 17:10 UTCEG score recompute
- 2026-09-05 15:28 UTCEPSS rescore
- 2026-09-05 09:49 UTCVendor advisory
Publicly available exploits
(10 references)Working exploit code is in the public domain (9 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCZwique/CVE-2025-49113First seen Aug 24, 2025
POC of CVE-2025-49113
Open source ↗ - GitHub PoC00xCanelo/CVE-2025-49113First seen Jul 19, 2025
💥 Python Exploit for CVE-2025-49113 | Roundcube Webmail RCE via PHP Object Injection
Open source ↗ - Exploit-DBEDB-52324First seen Jun 13, 2025
Roundcube 1.6.10 - Remote Code Execution (RCE)
Open source ↗ - GitHub PoCBiiTts/Roundcube-CVE-2025-49113First seen Jun 10, 2025
Proof-of-concept to CVE-2025-49113
Open source ↗ - GitHub PoCSyFi/CVE-2025-49113First seen Jun 6, 2025
CVE-2025-49113 exploit
Open source ↗ - GitHub PoChakaioffsec/CVE-2025-49113-exploitFirst seen Jun 6, 2025
Proof of Concept demonstrating Remote Code Execution through insecure deserialization in Roundcube (CVE-2025-49113).
Open source ↗ - Open source ↗GitHub PoCrasool13x/exploit-CVE-2025-49113First seen Jun 5, 2025
- Open source ↗GitHub PoCfearsoff-org/CVE-2025-49113First seen Jun 4, 2025
- GitHub PoCAdemking/CVE-2025-49113-nuclei-templateFirst seen Jun 4, 2025
CVE-2025-49113 - Roundcube <= 1.6.10 Post-Auth RCE via PHP Object Deserialization
Open source ↗ - GitHub PoCrxerium/CVE-2025-49113First seen Jun 3, 2025
Detection for CVE-2025-49113
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
- CVE-2004-0989EG 10.0EPSS p98HIGH
- CVE-2004-0990EG 10.0EPSS p98HIGH
- CVE-2004-1010EG 10.0EPSS p95HIGH
- CVE-2004-0941EG 10.0EPSS p96HIGH
- CVE-2004-0981EG 10.0EPSS p93HIGH
- CVE-2004-0882EG 10.0EPSS p96HIGH
- CVE-2004-0888EG 10.0EPSS p95HIGH
- CVE-2004-1012EG 10.0EPSS p93HIGH
- CVE-2004-1013EG 10.0EPSS p93HIGH
- CVE-2004-1018EG 10.0EPSS p97HIGH
Same CWE
10 shownCWE-502
- CVE-2017-10992EG 9.8EPSS p96CRITICAL
- CVE-2013-4521EG 9.8EPSS p90CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS p98CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-10934EG 9.8CRITICAL
- CVE-2016-9498EG 9.8EPSS p97CRITICAL
- CVE-2016-9483EG 9.8CRITICAL
- CVE-2015-2020EG 9.8CRITICAL
- CVE-2017-15692EG 9.8EPSS p92CRITICAL
Frequently asked(6)
What is CVE-2025-49113?
When was CVE-2025-49113 disclosed?
Is CVE-2025-49113 actively exploited?
What is the CVSS score of CVE-2025-49113?
Which products are affected by CVE-2025-49113?
How do I remediate CVE-2025-49113?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-49113
Is Your Infrastructure Affected by CVE-2025-49113?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.