Read the docs
TI-2026-53317 Aliases CVE-2026-76212GHSA-jj45-w38g-gfrj

phpMyFAQ before 4.1.7 LIKE Wildcard Injection via PostgreSQL

Priority HIGH 70CWE-88Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Code execution
Confidentiality · integrity · availability
None · None · Low
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-88.

Summary

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00428 37th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix Fixed phpMyFAQ (thorsten): 4.1.7

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
thorstenphpMyFAQ4.2.0-alpha to before 4.1.74.1.7Patch availableCNA
  • phpMyFAQ Vendorthorsten Affected 4.2.0-alpha to before 4.1.7 Fixed in 4.1.7 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*before 4.1.7Vulnerablethorsten
  • cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:* Versions before 4.1.7 Vulnerable ·thorsten

Remediation

  • Fix · CNA phpMyFAQ (thorsten) Fixed in 4.1.7

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    thorsten phpMyFAQ 4.1.7

    10 records Highest priority Priority HIGH 6 HIGH, 2 MEDIUM, 2 LOW

    Other records, highest priority first

    • TI-2026-53318 phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped ThrottlePriority HIGH 74
    • TI-2026-53146 phpMyFAQ before 4.1.7 Authentication Bypass via Tracking FilePriority HIGH 73
    • TI-2026-53310 phpMyFAQ before 4.1.7 SQL Injection via GlossaryPriority HIGH 72

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-76212
  2. 2026-10-03 Alias added: GHSA-jj45-w38g-gfrj

References

  • TI-2023-00296 Improper Authentication in thorsten/phpmyfaq CVSS 3.1CRITICAL 9.8
  • TI-2026-53313 phpMyFAQ 3.1.0 through 4.1.6 Authentication Bypass via LDAP CVSS 4.0HIGH 8.8
  • TI-2025-37331 phpMyFAQ duplicate email registration allows multiple accounts with the same email CVSS 3.1CRITICAL 9.8
  • TI-2024-36257 phpMyFAQ Generates an Error Message Containing Sensitive Information if database server is not available CVSS 3.1HIGH 8.6
  • TI-2023-03720 Improper Neutralization of Formula Elements in a CSV File in thorsten/phpmyfaq CVSS 3.1CRITICAL 9.8
  • TI-2023-00749 Command Injection in thorsten/phpmyfaq CVSS 3.1CRITICAL 9.8
See all 153 →

Sources