phpMyFAQ is an open source FAQ web application. The StopWords::add() method inversions prior to 4.1.6 builds a SQL INSERT statement using sprintf() and inserts the user-supplied stop word value directly into the query string without calling the application's database escaping function on it. A sibling method, StopWords::update(), which modifies an existing stop word, correctly escapes the same kind of input. The omission is isolated to the add() (insert) code path. An authenticated administrator who can reach the stop-word management feature can submit a crafted value as the "word" parameter that breaks out of the SQL string literal and injects arbitrary SQL, including statements to drop tables, exfiltrate data, or modify other rows in the database. Version 4.1.6 fixes the issue.
CVE-2026-56738
This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.5
- EG Score
- 8.5(low)
- EG Risk
- 43(Track)EG Risk 43/100SSVC: Track
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 computedSeverity85% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 24, 2026
Last Modified
September 24, 2026
Advisory Details (2)
Auto-updated Sep 24, 2026commit d56ef5d75c3c (thorsten/phpMyFAQ)
Patch available: thorsten/phpMyFAQ 4.1-nightly-2026-09-09 (contains commit d56ef5d75c3c)
https://github.com/thorsten/phpMyFAQ/commit/d56ef5d75c3c007de095bc4c13b470c7ac783f0fSQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion · Advisory · thorsten/phpMyFAQ · GitHub
https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-rw77-vq4g-x3hpVendor Advisories for CVE-2026-56738(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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.
- 2026-09-24 17:33 UTCEG score recompute
- 2026-09-24 16:37 UTCEG score recompute
- 2026-09-24 16:36 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-56738?
When was CVE-2026-56738 disclosed?
What is the CVSS score of CVE-2026-56738?
How do I remediate CVE-2026-56738?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56738
Is Your Infrastructure Affected by CVE-2026-56738?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.