Medium severity · published Apr 2, 2026
CVE-2026-34973
phpMyFAQ has a LIKE Wildcard Injection in Search.php — Unescaped % and _ Metacharacters Enable Broad Content Disclosure
5.3
CVSS
0.3%
EPSS
No
On KEV
Description
phpMyFAQ is an open source FAQ web application. Prior to version 4.1.1, the searchCustomPages() method in phpmyfaq/src/phpMyFAQ/Search.php uses real_escape_string() (via escape()) to sanitize the search term before embedding it in LIKE clauses. However, real_escape_string() does not escape SQL LIKE metacharacters % (match any sequence) and _ (match any single character). An unauthenticated attacker can inject these wildcards into search queries, causing them to match unintended records — including content that was not meant to be surfaced — resulting in information disclosure. This issue has been patched in version 4.1.1.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
Low
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 27% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
PH
phpMyFAQ · thorsten
< 4.1.1 · source: vendor, NVD
Affected product
PH
phpMyFAQ
thorsten
More from phpMyFAQ
9.8
CVE-2026-111911
phpMyFAQ 4.0.0 before 4.1.9 Authentication Bypass via WebAuthn Credential Injection
9.8
CVE-2026-46364
phpMyFAQ - SQL Injection via User-Agent Header in BuiltinCaptcha
9.4
CVE-2026-66398
phpMyFAQ before 4.1.6 Remote Code Execution via Configuration API
9.1
CVE-2026-45010
phpMyFAQ - Unauthenticated Two-Factor Authentication Brute-Force via /admin/check Endpoint
8.8
CVE-2026-75918
phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File