Advisory record · GHSA-rw77-vq4g-x3hp

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

CVSS 8.5 HighEPSS 0.0026 · 17th percentile

Published by the GitHub Advisory Database at 24 Sept 2026, 19:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
phpmyfaq/phpmyfaqPackagist<4.1.64.1.6
thorsten/phpmyfaqPackagist<4.1.64.1.6
Identifiers
GHSA-rw77-vq4g-x3hp · CVE-2026-56738 · PKSA-5kfv-yxk9-ft5p · PKSA-mq9q-wz1h-jkfd
Weakness (CWE)
CWE-89
Published
24 Sept 2026
Updated
24 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Packages phpmyfaq/phpmyfaq and thorsten/phpmyfaq are affected in versions below 4.1.6, and the fix is in 4.1.6. The StopWords::add() method inserts the submitted stop word into an SQL statement without escaping it, which allows SQL injection. An attacker needs valid administrator credentials, or an authenticated administrator session, to reach the stop-word form, and could then read, modify, or delete database data. Upgrade to version 4.1.6 or later.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.5 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0026, the 17th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:54 UTC First seen by agentprime
  2. 31 Oct 2026, 13:54 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.