SQL injection vulnerability in browse.php in phpMyRecipes 1.2.2 allows remote attackers to execute arbitrary SQL commands via the category parameter.
CVE-2014-9440
HIGHCVSS v2 · 7.57.5ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: other public exploit code (a GitHub or vendor proof of concept, or an Exploit-DB entry not marked verified).First public exploit code on record: 2014-12-23 (Exploit-DB EDB-35591)EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreLOW confidence
“—” beside the score: it is equal to NVD's CVSS v2 base score.
This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 2.3% exploitation probability in the next 30 days; it does not lift the v2 base. EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated) sets EG Risk's exploitation input, not EPSS. Confidence: LOW.
Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Also known asEUVD-2014-9261 (ENISA EUVD) · GHSA-9c72-r2f2-883r (GitHub Security Advisories)Source: ENISA EUVD
7.5EG
EchelonGraph verdictPlan mitigationNo fix on record since 2015: 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 on your normal schedule at low or medium mission impact and sooner than that at high, or retire the product (the SSVC decision on this page).
- Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 2.3%CVSS v2: 7.5Exploit: Public PoCExposed services: Not assessed
No fix has been recorded since the CVE record was published in 2015 — 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.
- CVSS v2.0 (legacy)
- 7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
- EG Score
- 7.5HIGHlow confidence
- EG Risk
- 50EG Risk 50/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.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, Track* at medium and Attend at high mission impact.Exploitation public PoC (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: No fix has been recorded since the CVE record was published in 2015. 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) on your normal schedule at low or medium mission impact and sooner than that at high, or retire the product. - EPSS PROB
- 2.3%
- EPSS %ILE
- 83rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v2.0 · CVSS v2.0AV:N/AC:L/Au:N/C:P/I:P/A:P
- EG Likelihood
- 2.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). 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
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA 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 SSVC and BOD 26-04 blocks below.
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 2015. 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) on your normal schedule at low or medium mission impact and sooner than that at high, or retire the product.
Exploitation public PoC (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.
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
January 2, 2015
Last Modified
May 6, 2026
References (3)
- MITRE · CVE Programhttp://packetstormsecurity.com/files/129789/PHP-Address-Book-Cross-Site-Scripting-SQL-Injection.html
- MITRE · CVE Programhttp://www.exploit-db.com/exploits/35591Exploit
- MITRE · CVE Programhttps://exchange.xforce.ibmcloud.com/vulnerabilities/99531
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 2015. 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-35591Published Dec 23, 2014
PHPMyRecipes 1.2.2 - 'browse.php?category' SQL Injection
Open source ↗
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2014-9440?
CVE-2014-9440 is a high-severity vulnerability; its CVE record was published on January 2, 2015. SQL injection vulnerability in browse.php in phpMyRecipes 1.2.2 allows remote attackers to execute arbitrary SQL commands via the category parameter.
When was CVE-2014-9440 made public?
CVE-2014-9440 was made public on December 23, 2014: 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 January 2, 2015. EchelonGraph's copy of the record carries a last-modified date of May 6, 2026; the record at its source may have been updated since.
Is CVE-2014-9440 actively exploited?
CVE-2014-9440 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.3% probability of exploitation in the next 30 days (83rd percentile of EPSS-scored CVEs).
How do I remediate CVE-2014-9440?
No fix for CVE-2014-9440 has been recorded since its CVE record was published in 2015. 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-2014-9440
Is Your Infrastructure Affected by CVE-2014-9440?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.