phpMyFAQ before 4.1.7 LIKE Wildcard Injection via PostgreSQL

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.

Scores

EPSS (exploitation in 30 days)

0.43% · top 63% of all CVEs (6 Nov 2026)

CISA SSVC

Exploitation: poc · Automatable: yes · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.9.

Weakness

• CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') (opens in a new tab)All about CWE-88 and its CVEs

Affected products

• thorsten · phpMyFAQ

  • affected 4.2.0-alpha – < 4.1.7
  • unaffected 4.1.7

References (2)

• GitHub Security Advisory (GHSA-5hx6-c293-588h) (opens in a new tab)vendor-advisoryexploit
• VulnCheck Advisory: phpMyFAQ before 4.1.7 LIKE Wildcard Injection via PostgreSQL (opens in a new tab)third-party-advisory

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-76212](https://trackcve.app/badge/CVE-2026-76212.svg)](https://trackcve.app/cve/CVE-2026-76212)

Record last updated 25 Aug 2026, 01:55 UTC.