phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion (CVE-2026-56738) | HOL Guard CVE

High · CVSS 8.5CVE-2026-56738GHSA-RW77-VQ4G-X3HP

phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion

Answer in brief

CVE-2026-56738 records a High severity (CVSS 8.5) vulnerability in phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion. The current sources do not mark it as known exploited. The current feed maps phpmyfaq/phpmyfaq (composer), thorsten/phpmyfaq (composer), thorsten/phpMyFAQ (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 24, 2026Updated Sep 24, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 24, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.5
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 8.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps phpmyfaq/phpmyfaq (composer), thorsten/phpmyfaq (composer), thorsten/phpMyFAQ (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
phpmyfaq/phpmyfaqcomposer	<=4.1.5	4.1.6
thorsten/phpmyfaqcomposer	<=4.1.5	4.1.6
thorsten/phpMyFAQgeneric	<4.1.6	4.1.6

Recommended response

Check inventory. Check lockfiles and deployed manifests for phpmyfaq/phpmyfaq, thorsten/phpmyfaq, thorsten/phpMyFAQ.
Review the reported fix. Update phpmyfaq/phpmyfaq to 4.1.6; thorsten/phpmyfaq to 4.1.6; thorsten/phpMyFAQ to 4.1.6 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source description

phpMyFAQ is an open source FAQ web application. The `StopWords::add()` method inversions prior to 4.1.6 builds a SQL `INSERT` statement using `sprintf()` and inserts the user-supplied stop word value directly into the query string without calling the application's database escaping function on it. A sibling method, `StopWords::update()`, which modifies an existing stop word, correctly escapes the same kind of input. The omission is isolated to the `add()` (insert) code path. An authenticated administrator who can reach the stop-word management feature can submit a crafted value as the "word" parameter that breaks out of the SQL string literal and injects arbitrary SQL, including statements to drop tables, exfiltrate data, or modify other rows in the database. Version 4.1.6 fixes the issue.

Quoted source text, attributed separately from HOL analysis.