phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| thorsten | phpMyFAQ | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Thorsten | Phpmyfaq |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-rw77-vq4g-x3hp | phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.261% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Thorsten
Thorsten phpmyfaq |
|
| Vendors & Products |
Thorsten
Thorsten phpmyfaq |
| 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
|