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.
Published: 2026-08-19
Score: 8.6 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

phpMyFAQ versions prior to 4.1.7 allow a SQL injection attack when creating or updating glossary entries because an escaped string is truncated before being incorporated into a SQL statement. The vulnerability arises when a user supplies a backslash that terminates the quoting sequence, enabling the execution of arbitrary SQL commands. The flaw permits the attacker to read confidential data stored in the database, thereby compromising the confidentiality of all stored information.

Affected Systems

The affected product is phpMyFAQ developed by thorsten. All releases before 4.1.7 are vulnerable, including the latest pre‑4.1.7 builds. No specific sub‑versions are listed beyond the general threshold.

Risk and Exploitability

The vulnerability requires that the attacker be an authenticated user with permissions to add or edit glossary entries, so privileged accounts can be leveraged. It is an injection flaw classified as CWE‑89. The CVSS score of 8.6 indicates high severity, but the EPSS score is 0.0023 (< 1%), indicating a very low but non‑zero exploitation probability. The vulnerability is not present in the CISA KEV catalog, suggesting no known public exploits yet, but the potential for privilege abuse and data leakage is substantial.

Generated by OpenCVE AI on August 20, 2026 at 16:37 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the vendor‑provided patch that raises the product version to 4.1.7 or later
  • Limit the ability to add or edit glossary entries to only trusted, least‑privileged accounts
  • Deploy a web application firewall or equivalent input validation layer to block malformed SQL payloads

Generated by OpenCVE AI on August 20, 2026 at 16:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 21 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Wed, 19 Aug 2026 21:15:00 +0000

Type Values Removed Values Added
First Time appeared Thorsten
Thorsten phpmyfaq
Vendors & Products Thorsten
Thorsten phpmyfaq

Wed, 19 Aug 2026 14:15:00 +0000

Type Values Removed Values Added
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.
Title phpMyFAQ before 4.1.7 SQL Injection via Glossary
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:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}

cvssV4_0

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


Subscriptions

Phpmyfaq Phpmyfaq
Thorsten Phpmyfaq
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-21T19:21:08.640Z

Reserved: 2026-08-19T11:34:28.576Z

Link: CVE-2026-76205

cve-icon Vulnrichment

Updated: 2026-08-21T19:21:04.175Z

cve-icon NVD

Status : Analyzed

Published: 2026-08-19T14:17:45.777

Modified: 2026-09-01T15:23:30.630

Link: CVE-2026-76205

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-20T16:45:16Z

Weaknesses
  • CWE-89

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