CVE-2012-2239

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.1 from GitHub Security Advisory published 2022-05-17. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.6%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Mahara 1.4.x before 1.4.4 and 1.5.x before 1.5.3 allows remote attackers to read arbitrary files or create TCP connections via an XML external entity (XXE) injection attack, as demonstrated by reading config.php.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
42
EG Risk 42/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 (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation1.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.6%
EPSS %ILE
74th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 24, 2012

Last Modified

April 29, 2026

Advisory Details (3)

Auto-updated Aug 1, 2026
Patch available.
Web page

Security announcements - XML External Entities Vulnerability in versions 1.4.3 and 1.5.2 - Mahara ePortfolio System

https://mahara.org/interaction/forum/topic.php?id=4869
Web page

Bug #1047111 “XEE possible in mahara” : Bugs : Mahara

https://bugs.launchpad.net/mahara/+bug/1047111
Web page

[SECURITY] [DSA 2591-1] mahara security update

http://www.debian.org/security/2012/dsa-2591

Affected Packages

(1 across 1 ecosystem)
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
mahara1.2.6-2 ... 1.2.6-2+squeeze5 (6 versions)
  • every version up to 1.2.6-2+squeeze6: fixed in 1.2.6-2+squeeze6
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 18× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 83 of 129 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 17 repeat rows among the latest 100 are merged into the row they repeat. The 46 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 01:38 UTCEG score recompute
  2. 2026-10-11 13:39 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  3. 2026-10-10 19:54 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  4. 2026-10-09 20:00 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  5. 2026-10-08 16:34 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  6. 2026-10-07 23:39 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  7. 2026-10-06 15:10 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  8. 2026-10-05 17:37 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  9. 2026-10-03 14:20 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  10. 2026-09-29 08:28 UTCEG score recompute
  11. 2026-09-28 13:44 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  12. 2026-09-27 13:39 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  13. 2026-09-26 15:52 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  14. 2026-09-24 13:57 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  15. 2026-09-20 20:08 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  16. 2026-09-16 13:58 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  17. 2026-09-15 03:04 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  18. 2026-09-13 16:40 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  19. 2026-09-11 09:30 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  20. 2026-09-07 15:56 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  21. 2026-09-05 15:22 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  22. 2026-09-04 13:55 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  23. 2026-08-28 21:34 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  24. 2026-08-27 14:20 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  25. 2026-08-26 14:40 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
Show 58 more
  1. 2026-08-23 00:12 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  2. 2026-08-21 23:43 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  3. 2026-08-19 16:59 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  4. 2026-08-18 13:42 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  5. 2026-08-16 02:09 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  6. 2026-08-15 01:25 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  7. 2026-08-09 13:42 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  8. 2026-08-08 16:31 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  9. 2026-08-07 16:21 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  10. 2026-08-06 13:41 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  11. 2026-08-05 19:12 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  12. 2026-08-04 15:04 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  13. 2026-07-30 01:26 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  14. 2026-07-28 15:31 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  15. 2026-07-25 14:12 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  16. 2026-07-23 14:14 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  17. 2026-07-23 01:07 UTCEG score recompute
  18. 2026-07-23 00:10 UTCEG score recompute
  19. 2026-07-22 21:49 UTCEG score recompute
  20. 2026-07-22 14:04 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  21. 2026-07-21 15:21 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  22. 2026-07-20 17:03 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  23. 2026-07-19 14:27 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  24. 2026-07-19 02:25 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  25. 2026-07-18 10:00 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  26. 2026-07-16 16:58 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  27. 2026-07-15 16:54 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  28. 2026-07-15 01:56 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  29. 2026-07-13 22:25 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  30. 2026-07-13 06:08 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  31. 2026-07-11 08:22 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  32. 2026-07-09 19:05 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  33. 2026-07-08 15:10 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  34. 2026-07-06 16:23 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  35. 2026-07-06 02:19 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  36. 2026-07-05 02:26 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  37. 2026-07-04 06:27 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  38. 2026-07-02 14:01 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  39. 2026-07-01 15:02 UTCEPSS rescoreEPSS 1.6% · 72nd percentile
  40. 2026-06-30 23:19 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  41. 2026-06-29 14:02 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  42. 2026-06-28 14:03 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  43. 2026-06-28 04:53 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  44. 2026-06-27 03:05 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  45. 2026-06-25 13:46 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  46. 2026-06-24 14:02 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  47. 2026-06-23 21:30 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  48. 2026-06-22 14:22 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  49. 2026-06-21 14:53 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  50. 2026-06-21 01:56 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  51. 2026-06-19 19:22 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  52. 2026-06-18 17:49 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  53. 2026-06-17 17:49 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  54. 2026-06-16 17:49 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  55. 2026-06-15 17:44 UTCEPSS rescoreEPSS 1.6% · 71st percentile
  56. 2026-06-14 23:14 UTCEPSS rescoreEPSS 0.4% · 58th percentile
  57. 2026-06-13 22:57 UTCEPSS rescoreEPSS 0.4% · 58th percentile
  58. 2026-06-12 23:08 UTCEPSS rescoreEPSS 0.4% · 58th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2012-2239?
CVE-2012-2239 is a critical-severity vulnerability; its CVE record was published on November 24, 2012. Mahara 1.4.x before 1.4.4 and 1.5.x before 1.5.3 allows remote attackers to read arbitrary files or create TCP connections via an XML external entity (XXE) injection attack, as demonstrated by reading config.php.
When was CVE-2012-2239 made public?
CVE-2012-2239 was made public on September 13, 2012: that is the date its CVE record's CNA, Debian GNU/Linux, gives for when the vulnerability was made public. The CVE record itself was published on November 24, 2012. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2012-2239 actively exploited?
CVE-2012-2239 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% probability of exploitation in the next 30 days (74th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2012-2239?
CVE-2012-2239 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2012-2239?
A fix for CVE-2012-2239 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-2012-2239

Explore →

Is Your Infrastructure Affected by CVE-2012-2239?

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

Book a Demo →Browse All CVEs