CVE-2026-76205
Received Received - Intake

phpMyFAQ Glossary SQL Injection via Truncated Escaped String

Publication date: 2026-08-19

Last updated on: 2026-08-19

Assigner: VulnCheck

Description
phpMyFAQ before 4.1.7 contains a SQL injection vulnerability in the glossary create and update endpoints caused by truncating an escaped string before embedding it in a SQL literal. Authenticated users with glossary add or edit permissions can craft a payload with a dangling backslash to escape the closing quote and inject arbitrary SQL commands to read sensitive database information.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-19
Last Modified
2026-08-19
Generated
2026-08-19
AI Q&A
2026-08-19
EPSS Evaluated
N/A
NVD
CVE-2026-76205
EUVD
EUVD-2026-62446

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
phpmyfaq phpmyfaq to 4.1.7 (exc)

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

This is a high-severity SQL injection vulnerability in phpMyFAQ versions 4.1.6 and earlier. It occurs in the glossary create and update functionality where user input is improperly sanitized before being used in SQL queries. The application escapes input but then truncates it, which can leave a dangling backslash that escapes the closing quote in the SQL query. This allows attackers to inject arbitrary SQL commands.

Detection Guidance

To detect this vulnerability, check if your phpMyFAQ instance is running a version before 4.1.7. Review the glossary create and update API endpoints for suspicious SQL-like input patterns or errors. Monitor database logs for unusual queries originating from these endpoints.

Impact Analysis

Authenticated users with glossary add or edit permissions (admin or editor roles) can exploit this vulnerability to inject malicious SQL commands. Successful exploitation enables full database access, including reading sensitive data like user credentials and configuration details, as well as potential database manipulation.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, which may violate compliance requirements under GDPR, HIPAA, or other regulations. Exposure of user credentials or personal data could result in legal penalties, reputational damage, and loss of trust.

Mitigation Strategies

Immediately upgrade phpMyFAQ to version 4.1.7 or later. Restrict glossary editing permissions to only trusted users. Review database access logs for signs of exploitation. Apply input validation and strict escaping for all user-controlled data in SQL queries.

Chat Assistant

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

EPSS Chart