Skip to main content
VulnerabilityPublished Updated

CVE-2026-76205: thorsten phpMyFAQ · SQL Injection

Affects thorsten phpMyFAQSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 4.1.7 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.1.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade phpMyFAQ and thorsten/phpMyFAQ to 4.1.7.

Affected software

ProductAffectedFixed in
thorstenphpMyFAQAffected
  • <4.1.7
Fixed in
  • 4.1.7
GitHubthorsten/phpMyFAQpkg:github/thorsten/phpMyFAQOther threatsAffected
  • <4.1.7
Fixed in
  • 4.1.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in phpMyFAQ version 4.1.7. Users should upgrade to version 4.1.7 or later to remediate this vulnerability. No additional mitigation guidance is provided in the vendor advisory.

Description

phpMyFAQ versions before 4.1.7 have a SQL injection vulnerability in the glossary create and update endpoints. Authenticated users with glossary add or edit permissions can exploit this by crafting a payload with a dangling backslash that escapes the closing quote, allowing arbitrary SQL commands to be injected. This vulnerability can lead to unauthorized reading of sensitive database information.

References

Community reviews

Loading reviews…