CVE-2026-76212 phpMyFAQ before 4.1.7 LIKE Wildcard Injection via PostgreSQL

Medium 6.9 Published 19 Aug 2026 Updated 25 Aug 2026

Unauthenticated attackers can cause denial of service in phpMyFAQ using PostgreSQL by exploiting wildcard injection in the search feature.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

What is CVE-2026-76212?

CVE-2026-76212 is a medium-severity denial of service vulnerability in Phpmyfaq Phpmyfaq, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-88

Which versions are affected by CVE-2026-76212?

It affects 1 product.

Products include Phpmyfaq Phpmyfaq.

How do I fix CVE-2026-76212?

No fix has been published for CVE-2026-76212 yet. Limit exposure of the affected software until one is available.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2026-76212 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76212 exists.

All Phpmyfaq Phpmyfaq vulnerabilities

Sources

Also known as GHSA-5hx6-c293-588h, GHSA-jj45-w38g-gfrj.