CVE-2009-1526

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this weekWeaponized

Also known asEUVD-2009-1522 (ENISA EUVD) · GHSA-hwc8-4222-xw22 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictPlan mitigationOn your normal schedule — no confirmed exploitation yet.
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS v2: —Exploit: Exploit-DB (verified)Exposed services: Not assessed

No fix has been recorded since the CVE record was published in 2009 — use a compensating control (WAF / firewall / segmentation) and check the vendor's advisory.

The CVE record's description, written by its CNA (MITRE Corporation), states the affected versions: "JBMC Software DirectAdmin before 1.334 allows local users to create or overwrite any file via a symlink attack on an arbitrary file in a certain temporary directory, related to a request for this temporary file in the P…" No release containing a fix is confirmed on record.

JBMC Software DirectAdmin before 1.334 allows local users to create or overwrite any file via a symlink attack on an arbitrary file in a certain temporary directory, related to a request for this temporary file in the PATH_INFO to the CMD_DB script during a backup action.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: 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

May 5, 2009

Last Modified

September 16, 2024

References (4)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 35× 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.

  1. 2026-11-01 16:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  2. 2026-10-31 16:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-30 16:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  4. 2026-10-29 18:29 UTCEG score recompute
  5. 2026-10-29 18:29 UTCGHSA enrichmentGHSA-hwc8-4222-xw22
  6. 2026-10-29 16:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  7. 2026-10-28 16:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  8. 2026-10-27 16:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  9. 2026-10-26 16:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  10. 2026-10-25 20:23 UTCEG score recompute
  11. 2026-10-25 16:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  12. 2026-10-24 16:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-10-23 16:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-10-22 16:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-10-21 16:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  16. 2026-10-20 16:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  17. 2026-10-19 16:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-10-18 16:25 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  19. 2026-10-18 11:44 UTCEG score recompute
  20. 2026-10-17 16:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  21. 2026-10-16 16:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  22. 2026-10-15 16:25 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  23. 2026-10-14 16:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  24. 2026-10-13 16:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  25. 2026-10-12 21:46 UTCEG score recompute
Show 36 more
  1. 2026-10-12 16:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  2. 2026-10-12 01:54 UTCEG score recompute
  3. 2026-10-11 13:38 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  4. 2026-10-10 19:54 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  5. 2026-10-09 20:00 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  6. 2026-10-08 16:33 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  7. 2026-10-07 23:37 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  8. 2026-10-06 15:09 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  9. 2026-10-05 17:37 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  10. 2026-10-04 23:15 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  11. 2026-09-30 14:58 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  12. 2026-09-29 07:58 UTCEG score recompute
  13. 2026-09-27 13:39 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  14. 2026-09-26 15:52 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  15. 2026-09-24 13:57 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  16. 2026-09-17 19:20 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  17. 2026-09-15 03:04 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  18. 2026-09-13 16:40 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  19. 2026-09-12 14:54 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  20. 2026-09-10 09:24 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  21. 2026-09-06 13:41 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  22. 2026-09-05 15:22 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  23. 2026-09-04 13:55 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  24. 2026-08-28 21:34 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  25. 2026-08-27 14:19 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  26. 2026-08-25 13:43 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  27. 2026-08-19 16:58 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  28. 2026-08-15 01:24 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  29. 2026-08-09 13:41 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  30. 2026-08-08 16:31 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  31. 2026-08-06 13:41 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  32. 2026-08-03 10:28 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  33. 2026-07-30 16:22 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  34. 2026-07-30 01:26 UTCEPSS rescoreEPSS 0.6% · 42nd percentile
  35. 2026-07-27 12:57 UTCEG score recompute
  36. 2026-07-27 12:57 UTCGHSA enrichmentGHSA-hwc8-4222-xw22

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). No fix has been recorded since the CVE record was published in 2009. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system.

  • Exploit-DBEDB-32947✓ verified
    Published Apr 22, 2009

    DirectAdmin 1.33.3 - '/CMD_DB' Backup Action Insecure Temporary File Creation

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2009-1526?
CVE-2009-1526 is a vulnerability whose severity is not yet rated; its CVE record was published on May 5, 2009. JBMC Software DirectAdmin before 1.334 allows local users to create or overwrite any file via a symlink attack on an arbitrary file in a certain temporary directory, related to a request for this temporary file in the PATH_INFO to the CMD_DB script during a backup action.
When was the CVE record for CVE-2009-1526 published?
The CVE record for CVE-2009-1526 was published on May 5, 2009. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 16, 2024; the record at its source may have been updated since.
Is CVE-2009-1526 actively exploited?
CVE-2009-1526 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
How do I remediate CVE-2009-1526?
No fix for CVE-2009-1526 has been recorded since its CVE record was published in 2009. Restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and check the vendor's advisory for a fix. The CVE record's description, written by its CNA (MITRE Corporation), states the affected versions: "JBMC Software DirectAdmin before 1.334 allows local users to create or overwrite any file via a symlink attack on an arbitrary file in a certain temporary directory, related to a request for this temporary file in the P…" No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2009-1526

Explore →

Is Your Infrastructure Affected by CVE-2009-1526?

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

Book a Demo →Browse All CVEs