CVE-2026-109573
Deferred Deferred - Pending Action

SQL Injection in phpMyFAQ via API Autocomplete

Publication date: 2026-10-12

Last updated on: 2026-10-12

Assigner: VulnCheck

Description
phpMyFAQ before 4.1.9 contains an SQL injection vulnerability in PdoMysql::escape(), which escapes single quotes with backslashes that are treated literally when MySQL or MariaDB runs in NO_BACKSLASH_ESCAPES mode. Unauthenticated attackers can send a Unicode right single quotation mark in the search parameter of api/autocomplete, which is normalized to an ASCII quote, to read credentials and configuration secrets, modify records, or drop tables.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-12
Last Modified
2026-10-12
Generated
2026-10-13
AI Q&A
2026-10-13
EPSS Evaluated
N/A
NVD
CVE-2026-109573

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
thorsten phpMyFAQ 0
thorsten phpMyFAQ 4.2.0-alpha

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

phpMyFAQ before version 4.1.9 has an SQL injection flaw in the PdoMysql::escape() function. When MySQL or MariaDB runs in NO_BACKSLASH_ESCAPES mode, single quotes escaped with backslashes are treated literally. Attackers can exploit this by sending a Unicode right single quotation mark in the search parameter of api/autocomplete, which gets normalized to an ASCII quote. This allows unauthorized access to read credentials, modify records, or drop tables.

Detection Guidance

Check if phpMyFAQ is running a vulnerable version (before 4.1.9) by inspecting the version in the application or server logs. Monitor HTTP requests to api/autocomplete with unusual Unicode right single quotation marks in the search parameter. Test for SQL injection by sending crafted inputs containing quotes and observing database responses.

Impact Analysis

Unauthenticated attackers could exploit this to read sensitive data like credentials and configuration secrets, alter or delete database records, or completely drop tables. This could lead to data breaches, loss of critical information, or system compromise.

Compliance Impact

This vulnerability could lead to unauthorized access and exposure of personal or sensitive data, violating GDPR and HIPAA requirements for data protection and confidentiality. Organizations using affected versions may face compliance violations, legal penalties, and reputational damage.

Mitigation Strategies

Upgrade phpMyFAQ to version 4.1.9 or later immediately. Disable NO_BACKSLASH_ESCAPES mode in MySQL or MariaDB if enabled. Implement input validation and sanitization for all API parameters, especially search fields. Restrict access to the api/autocomplete endpoint to trusted sources only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-109573. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart