Most recent entries from all

bdu:2026-15733

2026-10-06T15:48:51.751366+00:00

bdu:2026-15733

EUVD-2026-375335

2026-10-06T15:48:51.751410+00:00

EUVD-2026-375335

fkie_cve-2026-56738

2026-10-06T15:48:51.751428+00:00

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.

GHSA-rw77-vq4g-x3hp — phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion

2026-10-06T15:48:51.751481+00:00

Affected: Packagist: phpmyfaq/phpmyfaq, Packagist: thorsten/phpmyfaq

## Summary

The `StopWords::add()` method in phpMyFAQ 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.

---

## Affected Code

**File:** `phpmyfaq/src/phpMyFAQ/StopWords.php` **Method:** `add()` (approx. lines 60–75 in the audited revision)

```php $sql = sprintf( "INSERT INTO %s VALUES(%d, '%s', '%s')", $this->getTableName(), $id, $this->configuration->getDb()->escape($this->language), // language IS escaped $word // <-- $word is NOT escaped ); ```

`$word` is taken directly from the administrative form input (the new stop word to add) and concatenated into the SQL string via `sprintf("'%s'", ...)` with no call to the database driver's `escape()` method.

### Contrast with the safe sibling method

**Method:** `update()` (line 82 in the audited revision)

```php $this->configuration->getDb()-…