CVE-2026-76212

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM 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: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
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: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

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 computed
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

August 19, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Aug 19, 2026
Patch 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-postgresql
github 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-588h

Vendor 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 16× in last 7d / 82× 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.

  1. 2026-09-18 23:02 UTCEG score recompute
  2. 2026-09-18 23:02 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 21:35 UTCEG score recompute
  5. 2026-09-17 21:35 UTCGHSA enrichment
  6. 2026-09-16 20:08 UTCEG score recompute
  7. 2026-09-16 20:08 UTCGHSA enrichment
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 15:15 UTCEG score recompute
  11. 2026-09-15 15:15 UTCGHSA enrichment
  12. 2026-09-15 03:12 UTCEPSS rescore
  13. 2026-09-14 13:46 UTCEG score recompute
  14. 2026-09-14 13:46 UTCGHSA enrichment
  15. 2026-09-13 12:07 UTCEG score recompute
  16. 2026-09-13 12:07 UTCGHSA enrichment
  17. 2026-09-12 15:02 UTCEPSS rescore
  18. 2026-09-12 10:40 UTCEG score recompute
  19. 2026-09-12 10:40 UTCGHSA enrichment
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-11 09:13 UTCEG score recompute
  22. 2026-09-11 09:13 UTCGHSA enrichment
  23. 2026-09-10 09:35 UTCEPSS rescore
  24. 2026-09-10 07:46 UTCGHSA enrichment
  25. 2026-09-09 06:19 UTCEG score recompute
Show 62 more
  1. 2026-09-09 06:19 UTCGHSA enrichment
  2. 2026-09-08 22:01 UTCEPSS rescore
  3. 2026-09-08 04:53 UTCEG score recompute
  4. 2026-09-08 04:53 UTCGHSA enrichment
  5. 2026-09-07 03:26 UTCEG score recompute
  6. 2026-09-07 03:26 UTCGHSA enrichment
  7. 2026-09-06 13:48 UTCEPSS rescore
  8. 2026-09-06 01:44 UTCEG score recompute
  9. 2026-09-06 01:44 UTCGHSA enrichment
  10. 2026-09-05 00:18 UTCEG score recompute
  11. 2026-09-05 00:18 UTCGHSA enrichment
  12. 2026-09-04 05:07 UTCEPSS rescore
  13. 2026-09-03 22:49 UTCGHSA enrichment
  14. 2026-09-02 21:20 UTCEG score recompute
  15. 2026-09-02 21:20 UTCGHSA enrichment
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 15:59 UTCEG score recompute
  18. 2026-09-01 15:59 UTCGHSA enrichment
  19. 2026-09-01 13:54 UTCEPSS rescore
  20. 2026-09-01 04:40 UTCEPSS rescore
  21. 2026-09-01 04:40 UTCEPSS rescore
  22. 2026-08-31 20:41 UTCGHSA enrichment
  23. 2026-08-31 12:35 UTCEG score recompute
  24. 2026-08-31 12:35 UTCGHSA enrichment
  25. 2026-08-30 19:18 UTCEPSS rescore
  26. 2026-08-30 19:17 UTCEPSS rescore
  27. 2026-08-30 11:07 UTCEG score recompute
  28. 2026-08-30 11:07 UTCGHSA enrichment
  29. 2026-08-30 01:22 UTCEPSS rescore
  30. 2026-08-29 09:40 UTCEG score recompute
  31. 2026-08-29 09:40 UTCGHSA enrichment
  32. 2026-08-28 21:42 UTCEPSS rescore
  33. 2026-08-28 08:12 UTCEG score recompute
  34. 2026-08-28 08:12 UTCGHSA enrichment
  35. 2026-08-27 14:25 UTCEPSS rescore
  36. 2026-08-27 06:45 UTCEG score recompute
  37. 2026-08-27 06:45 UTCGHSA enrichment
  38. 2026-08-26 14:47 UTCEPSS rescore
  39. 2026-08-26 04:48 UTCEG score recompute
  40. 2026-08-26 04:48 UTCGHSA enrichment
  41. 2026-08-25 13:49 UTCEPSS rescore
  42. 2026-08-25 03:22 UTCEG score recompute
  43. 2026-08-25 03:22 UTCGHSA enrichment
  44. 2026-08-25 02:20 UTCEG score recompute
  45. 2026-08-25 02:20 UTCGHSA enrichment
  46. 2026-08-24 21:40 UTCEG score recompute
  47. 2026-08-24 21:40 UTCGHSA enrichment
  48. 2026-08-24 14:18 UTCEPSS rescore
  49. 2026-08-23 20:13 UTCEG score recompute
  50. 2026-08-23 20:13 UTCGHSA enrichment
  51. 2026-08-23 00:19 UTCEPSS rescore
  52. 2026-08-22 18:47 UTCEG score recompute
  53. 2026-08-22 18:47 UTCGHSA enrichment
  54. 2026-08-21 23:49 UTCEPSS rescore
  55. 2026-08-21 17:20 UTCEG score recompute
  56. 2026-08-21 17:20 UTCGHSA enrichment
  57. 2026-08-20 22:56 UTCEPSS rescore
  58. 2026-08-20 15:53 UTCEG score recompute
  59. 2026-08-20 15:53 UTCGHSA enrichment
  60. 2026-08-19 14:26 UTCEG score recompute
  61. 2026-08-19 14:12 UTCEG score recompute
  62. 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, with the most recent update on September 1, 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 76.1% 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

Explore →

Is Your Infrastructure Affected by CVE-2026-76212?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.