CVE-2025-30349

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2025-03-21. NVD baseline CVSS 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 31%CVSS: 7.2Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Horde IMP through 6.2.27, as used with Horde Application Framework through 5.2.23, allows XSS that leads to account takeover via a crafted text/html e-mail message with an onerror attribute (that may use base64-encoded JavaScript code), as exploited in the wild in March 2025.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
63
EG Risk 63/100

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
Severity72% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
31%
EPSS %ILE
98th
KEV
Not listed

Published

March 21, 2025

Last Modified

April 15, 2026

References (14)

Affected Packages

(2 across 2 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
php-horde-imp6.2.27-2
  • every version up to 6.2.27-2+deb11u1: fixed in 6.2.27-2+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
php-horde-imp6.2.27-3, 6.2.27-3.1
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 20× 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 171 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

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

  • GitHub PoCnatasaka/CVE-2025-30349
    First seen Mar 27, 2025

    Horde IMP (through 6.2.27) vulnerability – obfuscation via HTML encoding – XSS payload

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-30349?
CVE-2025-30349 is a high vulnerability published on March 21, 2025. Horde IMP through 6.2.27, as used with Horde Application Framework through 5.2.23, allows XSS that leads to account takeover via a crafted text/html e-mail message with an onerror attribute (that may use base64-encoded JavaScript code), as exploited in the wild in March 2025.
When was CVE-2025-30349 disclosed?
CVE-2025-30349 was first published on March 21, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-30349 actively exploited?
CVE-2025-30349 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-30349?
CVE-2025-30349 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2025-30349?
A fix for CVE-2025-30349 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-30349?

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

Book a Demo →Browse All CVEs