Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Phpmyfaq | Phpmyfaq | < 4.1.7 |
Related Weaknesses (CWE)
References
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-5hx6-c293-588hExploitMitigationVendor Advisory
- https://www.vulncheck.com/advisories/phpmyfaq-before-like-wildcard-injection-viaThird Party Advisory
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-5hx6-c293-588hExploitMitigationVendor Advisory
FAQ
What is CVE-2026-76212?
CVE-2026-76212 is a vulnerability with a CVSS score of 5.3 (MEDIUM). 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 escapeLike...
How severe is CVE-2026-76212?
CVE-2026-76212 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-76212?
Check the references section above for vendor advisories and patch information. Affected products include: Phpmyfaq Phpmyfaq.