CVE-2025-49113

CRITICALNVD 9.99.9—
EchelonGraph scoreHIGH confidence

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.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
9.9
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 95%CVSS: 9.9Exploit: NoneExposed: 0

A fix is available — apply it.

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 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 computed
Severity99% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
99.8%
KEV
⚠ Exploited

Published

June 2, 2025

Last Modified

February 23, 2026

Advisory Details (10)

Auto-updated Jul 20, 2026
Patch available. Sources: github_commit, github_pr, github_release.
generic

CVE-2025-49113 Roundcube Vulnerability Detection - vsociety

https://www.vicarius.io/vsociety/posts/cve-2025-49113-roundcube-vulnerability-detection
generic

CVE-2025-49113 Roundcube Mitigation Script - vsociety

https://www.vicarius.io/vsociety/posts/cve-2025-49113-roundcube-mitigation-script
generic

Security updates 1.6.11 and 1.5.10 released

https://roundcube.net/news/2025/06/01/security-updates-1.6.11-and-1.5.10
github_release Patch Available

Roundcube Webmail 1.6.11

Patch available: roundcube/roundcubemail 1.6.11

https://github.com/roundcube/roundcubemail/releases/tag/1.6.11
github_release Patch Available

Roundcube Webmail 1.5.10

Patch available: roundcube/roundcubemail 1.5.10

https://github.com/roundcube/roundcubemail/releases/tag/1.5.10
github_pr

Validate 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/9865
github_commit

commit c50a07d88ca3 (roundcube/roundcubemail)

Fix landed in roundcube/roundcubemail commit c50a07d88ca3 — awaiting tagged release

https://github.com/roundcube/roundcubemail/commit/c50a07d88ca38f018a0f4a0b008e9a1deb32637e
github_commit

commit 7408f3137966 (roundcube/roundcubemail)

Fix landed in roundcube/roundcubemail commit 7408f3137966 — awaiting tagged release

https://github.com/roundcube/roundcubemail/commit/7408f31379666124a39f9cb1018f62bc5e2dc695
github_commit

commit 0376f69e958a (roundcube/roundcubemail)

Fix landed in roundcube/roundcubemail commit 0376f69e958a — awaiting tagged release

https://github.com/roundcube/roundcubemail/commit/0376f69e958a8fef7f6f09e352c541b4e7729c4d
generic

Roundcube ≤ 1.6.10 Post-Auth RCE via PHP Object Deserialization [CVE-2025-49113]

https://fearsoff.org/research/roundcube

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubunturoundcube-sqlite3 (1.5.0+dfsg.1-2ubuntu0.1~esm4) @ jammy2026-07-22ubuntu

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

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
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 37× in last 7d / 165× 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 312 total refreshes for this CVE.

  1. 2026-07-23 02:57 UTCEG score recompute
  2. 2026-07-22 22:43 UTCEG score recompute
  3. 2026-07-22 22:43 UTCVendor advisory
  4. 2026-07-22 19:40 UTCCISA KEV update
  5. 2026-07-22 15:21 UTCVendor advisory
  6. 2026-07-21 14:37 UTCCISA KEV update
  7. 2026-07-21 02:45 UTCVendor advisory
  8. 2026-07-20 23:05 UTCVendor advisory
  9. 2026-07-20 19:25 UTCEG score recompute
  10. 2026-07-20 19:25 UTCVendor advisory
  11. 2026-07-20 17:07 UTCEPSS rescore
  12. 2026-07-20 15:45 UTCVendor advisory
  13. 2026-07-20 12:06 UTCVendor advisory
  14. 2026-07-20 08:26 UTCVendor advisory
  15. 2026-07-20 04:47 UTCVendor advisory
  16. 2026-07-20 01:07 UTCVendor advisory
  17. 2026-07-19 21:28 UTCVendor advisory
  18. 2026-07-19 17:48 UTCVendor advisory
  19. 2026-07-19 14:09 UTCVendor advisory
  20. 2026-07-19 10:30 UTCVendor advisory
  21. 2026-07-19 06:51 UTCVendor advisory
  22. 2026-07-19 03:11 UTCVendor advisory
  23. 2026-07-18 23:32 UTCVendor advisory
  24. 2026-07-18 19:52 UTCVendor advisory
  25. 2026-07-18 16:13 UTCVendor advisory
Show 75 more
  1. 2026-07-18 12:34 UTCVendor advisory
  2. 2026-07-18 08:54 UTCVendor advisory
  3. 2026-07-18 05:15 UTCVendor advisory
  4. 2026-07-17 21:56 UTCVendor advisory
  5. 2026-07-17 07:19 UTCEG score recompute
  6. 2026-07-16 23:59 UTCVendor advisory
  7. 2026-07-16 20:20 UTCVendor advisory
  8. 2026-07-16 17:04 UTCCISA KEV update
  9. 2026-07-16 16:40 UTCVendor advisory
  10. 2026-07-16 12:59 UTCVendor advisory
  11. 2026-07-16 09:19 UTCVendor advisory
  12. 2026-07-16 05:40 UTCVendor advisory
  13. 2026-07-16 02:01 UTCVendor advisory
  14. 2026-07-15 22:21 UTCVendor advisory
  15. 2026-07-15 18:42 UTCVendor advisory
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 16:49 UTCCISA KEV update
  19. 2026-07-15 15:04 UTCCISA KEV update
  20. 2026-07-15 11:23 UTCVendor advisory
  21. 2026-07-15 07:42 UTCVendor advisory
  22. 2026-07-15 04:04 UTCVendor advisory
  23. 2026-07-15 00:24 UTCVendor advisory
  24. 2026-07-14 20:45 UTCVendor advisory
  25. 2026-07-14 18:05 UTCCISA KEV update
  26. 2026-07-13 22:48 UTCVendor advisory
  27. 2026-07-13 19:09 UTCVendor advisory
  28. 2026-07-13 17:07 UTCCISA KEV update
  29. 2026-07-13 15:29 UTCVendor advisory
  30. 2026-07-13 11:50 UTCVendor advisory
  31. 2026-07-13 06:12 UTCEPSS rescore
  32. 2026-07-13 04:30 UTCVendor advisory
  33. 2026-07-13 00:51 UTCVendor advisory
  34. 2026-07-12 21:11 UTCVendor advisory
  35. 2026-07-12 13:51 UTCVendor advisory
  36. 2026-07-12 10:12 UTCVendor advisory
  37. 2026-07-12 06:32 UTCVendor advisory
  38. 2026-07-12 05:46 UTCEPSS rescore
  39. 2026-07-12 02:53 UTCVendor advisory
  40. 2026-07-11 23:14 UTCVendor advisory
  41. 2026-07-11 19:35 UTCVendor advisory
  42. 2026-07-11 15:56 UTCVendor advisory
  43. 2026-07-11 12:17 UTCVendor advisory
  44. 2026-07-11 08:38 UTCVendor advisory
  45. 2026-07-11 04:58 UTCVendor advisory
  46. 2026-07-11 01:19 UTCVendor advisory
  47. 2026-07-10 21:40 UTCVendor advisory
  48. 2026-07-10 18:01 UTCVendor advisory
  49. 2026-07-10 17:52 UTCCISA KEV update
  50. 2026-07-10 14:21 UTCVendor advisory
  51. 2026-07-09 23:40 UTCVendor advisory
  52. 2026-07-09 01:41 UTCVendor advisory
  53. 2026-07-08 22:01 UTCVendor advisory
  54. 2026-07-08 11:01 UTCVendor advisory
  55. 2026-07-08 07:22 UTCVendor advisory
  56. 2026-07-08 03:42 UTCVendor advisory
  57. 2026-07-08 00:01 UTCVendor advisory
  58. 2026-07-07 20:22 UTCVendor advisory
  59. 2026-07-07 19:01 UTCCISA KEV update
  60. 2026-07-07 17:16 UTCCISA KEV update
  61. 2026-07-07 16:43 UTCVendor advisory
  62. 2026-07-07 13:03 UTCVendor advisory
  63. 2026-07-07 09:23 UTCVendor advisory
  64. 2026-07-06 18:43 UTCVendor advisory
  65. 2026-07-06 16:27 UTCEPSS rescore
  66. 2026-07-06 16:27 UTCEPSS rescore
  67. 2026-07-06 11:24 UTCVendor advisory
  68. 2026-07-06 00:24 UTCVendor advisory
  69. 2026-07-05 17:04 UTCVendor advisory
  70. 2026-07-05 13:24 UTCVendor advisory
  71. 2026-07-05 09:44 UTCVendor advisory
  72. 2026-07-05 06:04 UTCVendor advisory
  73. 2026-07-05 02:25 UTCVendor advisory
  74. 2026-07-04 22:45 UTCVendor advisory
  75. 2026-07-04 15:26 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-49113
    First seen Aug 24, 2025

    POC of CVE-2025-49113

    Open source ↗
  • GitHub PoC00xCanelo/CVE-2025-49113
    First seen Jul 19, 2025

    💥 Python Exploit for CVE-2025-49113 | Roundcube Webmail RCE via PHP Object Injection

    Open source ↗
  • Exploit-DBEDB-52324
    First seen Jun 13, 2025

    Roundcube 1.6.10 - Remote Code Execution (RCE)

    Open source ↗
  • GitHub PoCBiiTts/Roundcube-CVE-2025-49113
    First seen Jun 10, 2025

    Proof-of-concept to CVE-2025-49113

    Open source ↗
  • GitHub PoCSyFi/CVE-2025-49113
    First seen Jun 6, 2025

    CVE-2025-49113 exploit

    Open source ↗
  • GitHub PoChakaioffsec/CVE-2025-49113-exploit
    First seen Jun 6, 2025

    Proof of Concept demonstrating Remote Code Execution through insecure deserialization in Roundcube (CVE-2025-49113).

    Open source ↗
  • GitHub PoCrasool13x/exploit-CVE-2025-49113
    First seen Jun 5, 2025
    Open source ↗
  • GitHub PoCfearsoff-org/CVE-2025-49113
    First seen Jun 4, 2025
    Open source ↗
  • GitHub PoCAdemking/CVE-2025-49113-nuclei-template
    First seen Jun 4, 2025

    CVE-2025-49113 - Roundcube <= 1.6.10 Post-Auth RCE via PHP Object Deserialization

    Open source ↗
  • GitHub PoCrxerium/CVE-2025-49113
    First seen Jun 3, 2025

    Detection for CVE-2025-49113

    Open source ↗

Frequently asked(6)

What is CVE-2025-49113?
CVE-2025-49113 is a critical vulnerability published on June 2, 2025. 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.
When was CVE-2025-49113 disclosed?
CVE-2025-49113 was first published in the National Vulnerability Database on June 2, 2025, with the most recent update on February 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-49113 actively exploited?
Yes. CISA added CVE-2025-49113 to the Known Exploited Vulnerabilities catalog on February 20, 2026, affecting Roundcube Webmail. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2025-49113?
CVE-2025-49113 has a CVSS v3 base score of 9.9 (NVD).
Which products are affected by CVE-2025-49113?
CVE-2025-49113 affects Roundcube Webmail. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2025-49113?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-49113, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-49113

Explore →

Is Your Infrastructure Affected by CVE-2025-49113?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs