CVE-2024-42009

CRITICALNVD 9.39.3
EchelonGraph scoreHIGH confidence

Score elevated to 9.3 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-06-09), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.3 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
9.3EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 80%CVSS: 9.3Exploit: cisa kev · ssvc active · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

A Cross-Site Scripting vulnerability in Roundcube through 1.5.7 and 1.6.x through 1.6.7 allows a remote attacker to steal and send emails of a victim via a crafted e-mail message that abuses a Desanitization issue in message_body() in program/actions/mail/show.php.

CVSS v3
9.3
EG Score
9.3(high)
EG Risk
82(Attend)
EG Risk 82/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
Severity93% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
80%
EPSS %ILE
100%
KEV
⚠ Exploited

Published

August 5, 2024

Last Modified

November 4, 2025

Advisory Details (6)

Auto-updated Aug 1, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github_release, cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-42009
generic🟡 PoC Available

Government Emails at Risk: Critical Cross-Site Scripting Vulnerability in Roundcube Webmail | Sonar

https://sonarsource.com/blog/government-emails-at-risk-critical-cross-site-scripting-vulnerability-in-roundcube-webmail/
generic

Security updates 1.6.8 and 1.5.8 released

https://roundcube.net/news/2024/08/04/security-updates-1.6.8-and-1.5.8
github_release Patch Available

Roundcube Webmail 1.6.8

Patch available: roundcube/roundcubemail 1.6.8

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

Roundcube Webmail 1.5.8

Patch available: roundcube/roundcubemail 1.5.8

https://github.com/roundcube/roundcubemail/releases/tag/1.5.8
generic

Releases · roundcube/roundcubemail · GitHub

https://github.com/roundcube/roundcubemail/releases

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubunturoundcube-sqlite3 (1.6.6+dfsg-2ubuntu0.1+esm1) @ noble2026-08-04ubuntu

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.

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 85× in last 7d / 306× 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 762 total refreshes for this CVE.

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

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCDaniTheHack3r/CVE-2024-42009-PoC
    First seen May 24, 2025

    CVE-2024-42009 Proof of Concept

    Open source ↗
  • GitHub PoC0xbassiouny1337/CVE-2024-42009
    First seen Feb 11, 2025

    This script exploits a stored XSS vulnerability (CVE-2024-42009) in Roundcube Webmail version 1.6.7. It injects a malicious payload into the webmail system, which, when triggered, exfiltrates email content from the victim’s inbox.

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-42009.yaml
    First seen Jan 1, 2024

    Roundcube Webmail - Cross-Site Scripting

    Open source ↗

Frequently asked(6)

What is CVE-2024-42009?
CVE-2024-42009 is a critical vulnerability published on August 5, 2024. A Cross-Site Scripting vulnerability in Roundcube through 1.5.7 and 1.6.x through 1.6.7 allows a remote attacker to steal and send emails of a victim via a crafted e-mail message that abuses a Desanitization issue in message_body() in program/actions/mail/show.php.
When was CVE-2024-42009 disclosed?
CVE-2024-42009 was first published in the National Vulnerability Database on August 5, 2024, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-42009 actively exploited?
Yes. CISA added CVE-2024-42009 to the Known Exploited Vulnerabilities catalog on June 9, 2025, affecting Roundcube Webmail. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2024-42009?
CVE-2024-42009 has a CVSS v3 base score of 9.3 (NVD).
Which products are affected by CVE-2024-42009?
CVE-2024-42009 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-2024-42009?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-42009, 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

Explore the affected products and dependency analysis for CVE-2024-42009

Explore →

Is Your Infrastructure Affected by CVE-2024-42009?

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