CVE-2026-76212: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') in thorsten phpMyFAQ
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.
AI Analysis
Technical Summary
In phpMyFAQ before version 4.1.7 and including 4.2.0-alpha, when using the native pgsql PHP extension for PostgreSQL, the declared LIKE ESCAPE character ('=') in the Search/Database/Pgsql.php backend is incorrect. The escapeLikeWildcards() function escapes user input with a '|' prefix, causing wildcard escaping to be ineffective. Consequently, user-supplied '%' and '_' characters remain active as LIKE wildcards. An unauthenticated attacker can exploit this by submitting such characters in the public FAQ search form, triggering broad pattern matches and expensive sequential scans that result in denial of service. The PDO PostgreSQL backend is not affected, and quotes remain escaped, so this vulnerability does not lead to SQL injection or data exfiltration.
Potential Impact
An unauthenticated attacker can cause denial of service by submitting specially crafted input containing wildcard characters in the public FAQ search form. This forces broad pattern matches and resource-intensive sequential scans on the database, potentially degrading or disrupting service availability. There is no risk of SQL injection or data leakage from this vulnerability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, consider disabling the native pgsql PHP extension backend or restricting access to the public FAQ search form to mitigate denial of service risk. The PDO PostgreSQL backend is not affected and can be used as an alternative.
CVE-2026-76212: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') in thorsten phpMyFAQ
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.
CVSS v4.0
Score 6.9medium
Affected software
pkg:github/thorsten/phpMyFAQRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In phpMyFAQ before version 4.1.7 and including 4.2.0-alpha, when using the native pgsql PHP extension for PostgreSQL, the declared LIKE ESCAPE character ('=') in the Search/Database/Pgsql.php backend is incorrect. The escapeLikeWildcards() function escapes user input with a '|' prefix, causing wildcard escaping to be ineffective. Consequently, user-supplied '%' and '_' characters remain active as LIKE wildcards. An unauthenticated attacker can exploit this by submitting such characters in the public FAQ search form, triggering broad pattern matches and expensive sequential scans that result in denial of service. The PDO PostgreSQL backend is not affected, and quotes remain escaped, so this vulnerability does not lead to SQL injection or data exfiltration.
Potential Impact
An unauthenticated attacker can cause denial of service by submitting specially crafted input containing wildcard characters in the public FAQ search form. This forces broad pattern matches and resource-intensive sequential scans on the database, potentially degrading or disrupting service availability. There is no risk of SQL injection or data leakage from this vulnerability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, consider disabling the native pgsql PHP extension backend or restricting access to the public FAQ search form to mitigate denial of service risk. The PDO PostgreSQL backend is not affected and can be used as an alternative.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-19T11:34:28.577Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a85bc76acd9273b492f4986
Added to database: 08/19/2026, 14:23:50 UTC
Last enriched: 08/19/2026, 14:55:18 UTC
Last updated: 08/19/2026, 17:55:42 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.