Skip to main content

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

0
High
VulnerabilityCVE-2026-56738cvecve-2026-56738cwe-89
Published: 09/24/2026 (09/24/2026, 16:35:02 UTC)
Source: CVE Database V5
Vendor/Project: thorsten
Product: phpMyFAQ

Description

phpMyFAQ versions prior to 4.1.6 contain an SQL injection vulnerability in the StopWords::add() method. This method improperly constructs an SQL INSERT statement by directly inserting user-supplied input without proper escaping. An authenticated administrator with access to the stop-word management feature can exploit this to inject arbitrary SQL commands. The issue is fixed in version 4.1.6.

CVSS v4.0

Score 8.5high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
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:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Affected software

thorsten

phpMyFAQ

Affected versions
<4.1.6
GitHub Actionsmore threats →ai
thorsten/phpMyFAQ
pkg:github/thorsten/phpMyFAQ
Affected versions
<4.1.6

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/24/2026, 17:02:49 UTC

Technical Analysis

The vulnerability in phpMyFAQ arises from the StopWords::add() method, which uses sprintf() to build an SQL INSERT statement and inserts user input directly without escaping. This allows an authenticated administrator to inject arbitrary SQL via the 'word' parameter, potentially leading to data manipulation or destruction. The StopWords::update() method correctly escapes input, isolating the flaw to the add() path. Version 4.1.6 addresses this issue by applying proper escaping.

Potential Impact

An authenticated administrator can exploit this vulnerability to execute arbitrary SQL commands, including dropping tables, exfiltrating data, or modifying database rows. This can compromise the integrity and confidentiality of the application's database.

Mitigation Recommendations

Upgrade phpMyFAQ to version 4.1.6 or later, where this SQL injection vulnerability has been fixed. No additional mitigation is required once the update is applied.

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
GitHub_M
Date Reserved
2026-06-22T19:17:28.959Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ab5545bf7a7c5410690de38

Added to database: 09/24/2026, 16:48:27 UTC

Last enriched: 09/24/2026, 17:02:49 UTC

Last updated: 09/24/2026, 17:13:54 UTC

Views: 5

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