CVE-2026-76212
Last modified
CVE-2026-76212 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. 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. EPSS estimates a 0.30% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Phpmyfaq | Phpmyfaq | < 4.1.7 |
References
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-5hx6-c293-588hExploit, Mitigation, Vendor Advisory
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-5hx6-c293-588hExploit, Mitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-76212?
How severe is CVE-2026-76212?
How do I fix CVE-2026-76212?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-76207phpMyFAQ before 4.1.7 contains a two-factor authentication b…8.1
- CVE-2026-76208phpMyFAQ versions 3.1.0 through 4.1.6 contain an authenticat…8.2
- CVE-2026-76209phpMyFAQ versions before v4.1.6 fail to validate the securit…4.3
- CVE-2026-7621The SMTP2GO for WordPress – Email Made Easy plugin for WordP…4.3
- CVE-2026-76210phpMyFAQ before 4.1.6 does not adequately sanitize HTML in F…6.5
- CVE-2026-76211phpMyFAQ before 4.1.7 fails to properly enforce CONFIGURATIO…4.3
- CVE-2026-76213phpMyFAQ before 4.1.7 contains a brute-force vulnerability i…7.4
- CVE-2026-76214phpMyFAQ before 4.1.7 fails to persist the WebAuthn login ch…7.4
- CVE-2026-76215phpMyFAQ before 4.1.7 fails to apply parent FAQ visibility c…5.3
- CVE-2026-76216Vikunja through 2.4.0 contains a principal-type confusion vu…7.5
- CVE-2026-76217GitPython versions before 3.1.58 fail to validate options pa…6.5
- CVE-2026-76218GitPython before 3.1.58 contains a remote code execution vul…8.8
Are you affected by CVE-2026-76212?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
