CVE-2009-1936

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekWeaponized
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 42%CVSS: 9.8Exploit: Exploit-DB (verified)Exposed services: Not assessed

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 not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

_functions.php in cpCommerce 1.2.x, possibly including 1.2.9, sends a redirect but does not exit when it is called directly, which allows remote attackers to bypass a protection mechanism to conduct remote file inclusion and directory traversal attacks, execute arbitrary PHP code, or read arbitrary files via the GLOBALS[prefix] parameter, a different vector than CVE-2003-1500.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
85
EG Risk 85/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: 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 within your standard update timelines at low or medium mission impact and sooner than that at high; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
42%
EPSS %ILE
98th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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 within your standard update timelines at low or medium mission impact and sooner than that at high; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

June 5, 2009

Last Modified

April 23, 2026

Advisory Details (3)

Auto-updated Oct 8, 2026
No fix on record since 2009.
Web page

CPCommerce 1.2.x - 'GLOBALS[prefix]' Arbitrary File Inclusion - PHP webapps Exploit

https://www.exploit-db.com/exploits/8790
Web page

CVE-2009-1936 - PSIRT.COM

http://www.securityfocus.com/bid/35103
Web page

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/35245

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 20× 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 80 of 110 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. 20 repeat rows among the latest 100 are merged into the row they repeat. The 30 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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 or retire the product.

  • Exploit-DBEDB-8790✓ verified
    Published May 26, 2009

    CPCommerce 1.2.x - 'GLOBALS[prefix]' Arbitrary File Inclusion

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2009-1936?
CVE-2009-1936 is a critical-severity vulnerability; its CVE record was published on June 5, 2009. _functions.php in cpCommerce 1.2.x, possibly including 1.2.9, sends a redirect but does not exit when it is called directly, which allows remote attackers to bypass a protection mechanism to conduct remote file inclusion and directory traversal attacks, execute arbitrary PHP code, or read arbitrary…
When was CVE-2009-1936 made public?
CVE-2009-1936 was made public on May 26, 2009: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on June 5, 2009. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2009-1936 actively exploited?
CVE-2009-1936 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 42% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2009-1936?
CVE-2009-1936 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2009-1936?
No fix for CVE-2009-1936 has been recorded since its 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 (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2009-1936?

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

Book a Demo →Browse All CVEs