CVE-2026-109573

phpMyFAQ before 4.1.9 SQL Injection via api/autocomplete Search Endpoint

Published Oct 12, 2026 CVSS 4.0 · 9.2 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

phpMyFAQ before version 4.1.9 contains an SQL injection flaw in the PdoMysql::escape() routine. The routine incorrectly escapes single quotes when the database server runs in NO_BACKSLASH_ESCAPES mode, allowing a crafted Unicode right single quotation mark to be normalized to a literal ASCII quote. This injection can be performed via the publicly accessible api/autocomplete endpoint and grants an unauthenticated attacker read access to credentials and configuration secrets, the ability to modify records, or even drop tables. This weakness is a classic SQL injection, identified as CWE-89.

Affected Systems

The vulnerability applies to phpMyFAQ releases prior to 4.1.9 from Thorsten. It requires a MySQL or MariaDB database configured with the NO_BACKSLASH_ESCAPES option and exposure of the api/autocomplete endpoint. Any installation of phpMyFAQ on such a database is vulnerable, regardless of the operating system, as the vulnerability resides in the PHP code.

Risk and Exploitability

The CVSS score of 9.2 classifies the flaw as critical. The EPSS score is not available, but the lack of authentication and the simplicity of sending a crafted GET request to the endpoint mean exploitation is straightforward for automated scanners. The vulnerability is not listed in the CISA KEV catalog. Attackers can execute the exploit without needing elevated privileges or prior access, making it a high‑risk threat to systems where phpMyFAQ is exposed to the network.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update phpMyFAQ to version 4.1.9 or later to apply the fixed escape routine.
  • Limit access to the api/autocomplete endpoint, allowing only authenticated or internal users while the upgrade is pending.
  • Review and replace any custom SQL strings in phpMyFAQ with prepared statements or parameterized queries to eliminate injection vectors.

Generated by OpenCVE AI on October 13, 2026 at 00:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title phpMyFAQ before 4.1.9 SQL Injection via api/autocomplete Search Endpoint
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-89
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.2, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 13, 2026, 1:52 PM
Reserved
Oct 12, 2026, 7:27 PM
Status
Deferred
Published
Oct 12, 2026, 11:17 PM
Modified
Oct 13, 2026, 2:17 PM