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.
CVE-2026-76212
MEDIUMPre-NVD 5.35.3—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 5.3 from GitHub Security Advisory published 2026-08-19. a secondary CVSS source baseline 5.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026Patch available. Sources: github.
generic
phpMyFAQ before 4.1.7 LIKE Wildcard Injection via PostgreSQL | Advisories | VulnCheck
https://www.vulncheck.com/advisories/phpmyfaq-before-like-wildcard-injection-via-postgresqlgithub Patch Available
PostgreSQL search backend declares the wrong LIKE ESCAPE character, so the wildcard-escaping fix is inert on that backend · Advisory · thorsten/phpMyFAQ · GitHub
https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-5hx6-c293-588hVendor Advisories for CVE-2026-76212(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 15:53 UTCEG score recompute
- 2026-08-20 15:53 UTCGHSA enrichment
- 2026-08-19 14:26 UTCEG score recompute
- 2026-08-19 14:12 UTCEG score recompute
- 2026-08-19 14:12 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-76212?
CVE-2026-76212 is a medium vulnerability published on August 19, 2026. 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…
When was CVE-2026-76212 disclosed?
CVE-2026-76212 was first published in the National Vulnerability Database on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76212 actively exploited?
CVE-2026-76212 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.4% of all scored CVEs.
What is the CVSS score of CVE-2026-76212?
CVE-2026-76212 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-76212?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76212, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76212
Is Your Infrastructure Affected by CVE-2026-76212?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.