Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-rw77-vq4g-x3hp | phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion |
Thu, 24 Sep 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Thorsten
Thorsten phpmyfaq |
|
| Vendors & Products |
Thorsten
Thorsten phpmyfaq |
Thu, 24 Sep 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-24T16:35:02.670Z
Reserved: 2026-06-22T19:17:28.959Z
Link: CVE-2026-56738
No data.
Status : Deferred
Published: 2026-09-24T17:17:04.890
Modified: 2026-09-24T17:17:05.003
Link: CVE-2026-56738
No data.
OpenCVE Enrichment
Updated: 2026-09-24T19:00:15Z
Github GHSA