The vulnerability of the `StopWords::add()` method in the phpMyFAQ web application’s file `phpMyFAQ/src/phpMyFAQ/StopWords.php` allows a attacker to compromise the confidentiality and integrity of the protected information.

The vulnerability of the StopWords::add method in the phpMyFAQ web application’s file phpMyFAQ/src/phpMyFAQ/StopWords.php relates to the lack of measures taken to protect the SQL query structure when processing the word parameter. Exploiting this vulnerability allows an attacker to compromise the...

GHSA-RW77-VQ4G-X3HP phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion

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 existin...

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

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 existin...

CVE-2026-56738

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 siblin...

CVE-2026-56738

The open-source FAQ web application phpMyFAQ is vulnerable to SQL Injection in the StopWords::add() method in versions prior to 4.1.6 . The root cause is the direct insertion of user-supplied stop word values into a SQL INSERT statement using sprintf() without proper database escaping. While the ...

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

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 siblin...

EUVD-2026-86289

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 siblin...

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

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 siblin...

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

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 siblin...

PT-2026-98142

Name of the Vulnerable Software and Affected Versions phpMyFAQ versions prior to 4.1.6 Description An issue exists in the StopWords::add function where user-supplied input is inserted into a SQL INSERT statement using sprintf without proper database escaping. This occurs specifically in the code...

CVE-2026-56738: Improper Neutralization of Special Elements used in an SQL Command

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 siblin...