Skip to main content
EPSS 0.4%top 65%

CVE-2026-76205: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in thorsten phpMyFAQ

0
High
Published: 08/19/2026 (08/19/2026, 14:01:53 UTC)
Source: CVE Database V5
Vendor/Project: thorsten
Product: phpMyFAQ

Description

phpMyFAQ versions before 4.1.7 have a SQL injection vulnerability in the glossary create and update endpoints. Authenticated users with glossary add or edit permissions can exploit this by crafting a payload with a dangling backslash that escapes the closing quote, allowing arbitrary SQL commands to be injected. This vulnerability can lead to unauthorized reading of sensitive database information.

CVSS v4.0

Score 8.6high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
High
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

thorsten

phpMyFAQ

Affected versions
>=0 <4.1.7
GitHub Actionsmore threats →ai
thorsten/phpMyFAQ
pkg:github/thorsten/phpMyFAQ
Affected versions
<4.1.7

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/11/2026, 08:49:22 UTC

Technical Analysis

CVE-2026-76205 is a SQL injection vulnerability in phpMyFAQ prior to version 4.1.7. The flaw occurs because an escaped string is truncated before being embedded in a SQL literal in the glossary create and update endpoints. Authenticated users with glossary add or edit permissions can exploit this by using a payload with a dangling backslash to escape the closing quote, enabling injection of arbitrary SQL commands to access sensitive data.

Potential Impact

Successful exploitation allows authenticated users with specific glossary permissions to read sensitive information from the database by injecting arbitrary SQL commands. This can compromise data confidentiality within the affected phpMyFAQ installation.

Mitigation Recommendations

A fix is available in phpMyFAQ version 4.1.7. Users should upgrade to version 4.1.7 or later to remediate this vulnerability. No additional mitigation guidance is provided in the vendor advisory.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-08-19T11:34:28.576Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6a85bc6bacd9273b492f4870

Added to database: 08/19/2026, 14:23:39 UTC

Last enriched: 09/11/2026, 08:49:22 UTC

Last updated: 10/04/2026, 10:02:29 UTC

Views: 59

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses