CVE-2026-76212: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') in thorsten phpMyFAQ
Description
phpMyFAQ versions before 4.1.7, when using the native pgsql PHP extension for PostgreSQL, improperly handle wildcard escaping in SQL LIKE queries. This flaw allows unauthenticated attackers to submit wildcard characters in the public FAQ search form, causing broad pattern matches and expensive sequential scans that can lead to denial of service. The issue does not affect the PDO PostgreSQL backend and does not enable SQL injection or data exfiltration.
CVSS v4.0
Score 6.9medium
Affected software
thorsten
phpMyFAQ
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
phpMyFAQ before version 4.1.7, when configured with the native pgsql PHP extension for PostgreSQL, incorrectly declares the LIKE ESCAPE character as '=' in the Search/Database/Pgsql.php backend. Meanwhile, the escapeLikeWildcards() function escapes user input with the '|' prefix, rendering wildcard escaping 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 costly sequential scans that result in denial of service. The PDO PostgreSQL backend is unaffected, and quote escaping remains intact, preventing SQL injection or data exfiltration.
Potential Impact
An unauthenticated attacker can cause a denial of service by submitting wildcard characters in the public FAQ search form, leading to expensive database queries and resource exhaustion. There is no risk of SQL injection or data leakage from this vulnerability.
Mitigation Recommendations
Patch to phpMyFAQ version 4.1.7 or later where this issue is fixed. If upgrading is not immediately possible, consider disabling the native pgsql PHP extension backend or restricting access to the public FAQ search form to mitigate denial of service risk. Patch status is not yet confirmed explicitly in the provided data; check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-19T11:34:28.577Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a85bc76acd9273b492f4986
Added to database: 08/19/2026, 14:23:50 UTC
Last enriched: 09/11/2026, 08:48:34 UTC
Last updated: 10/04/2026, 10:02:29 UTC
Views: 70
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.