phpMyFAQ before 4.1.7, when configured to use PostgreSQL via the native pgsql PHP extension, declares an incorrect LIKE ESCAPE character ('=') in the Search/Database/Pgsql.php backend while escapeLikeWildcards() escapes user input with the '|' prefix. As a result, wildcard escaping is a no-op and user-supplied % and _ characters remain active LIKE wildcards. An unauthenticated attacker can submit such characters in the public FAQ search form to force maximally broad pattern matches and expensive sequential scans, resulting in a denial of service. The PDO PostgreSQL backend is not affected, and quotes remain escaped so this does not enable quote-breaking SQL injection or data exfiltration.
References
| Link | Resource |
|---|---|
| https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-5hx6-c293-588h | Exploit Mitigation Vendor Advisory |
| https://www.vulncheck.com/advisories/phpmyfaq-before-like-wildcard-injection-via-postgresql | Third Party Advisory |
| https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-5hx6-c293-588h | Exploit Mitigation Vendor Advisory |
Configurations
History
No history.
Information
Published : 2026-08-19 14:17
Updated : 2026-09-01 15:20
NVD link : CVE-2026-76212
Mitre link : CVE-2026-76212
CVE.ORG link : CVE-2026-76212
JSON object : View
Products Affected
phpmyfaq
- phpmyfaq
CWE
CWE-88
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
