CVE-2026-76212

published 19 Aug 2026 · updated 25 Aug 2026

phpMyFAQ before 4.1.7 LIKE Wildcard Injection via PostgreSQL

5.3MediumCVSS 5.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 4.1.7.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
thorsten>=4.2.0-alpha <4.1.74.1.7

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-76212 severity on Zeptric[![CVE-2026-76212](https://zeptric.io/badge/cve/CVE-2026-76212.svg)](https://zeptric.io/cve/CVE-2026-76212)