Vulnerability Description
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.
Related Weaknesses (CWE)
References
- https://github.com/thorsten/phpMyFAQ/commit/d56ef5d75c3c007de095bc4c13b470c7ac78
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-rw77-vq4g-x3hp
FAQ
What is CVE-2026-56738?
CVE-2026-56738 is a documented vulnerability. 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 ...
How severe is CVE-2026-56738?
CVSS scoring is not yet available for CVE-2026-56738. Check NVD for updates.
Is there a patch for CVE-2026-56738?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.