Skip to main content
VulnerabilityPublished

CVE-2026-130352: thorsten phpMyFAQ · Insertion of Sensitive Information Into Sent Data

Affects thorsten phpMyFAQSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.2.0-RC.2 or 4.1.12 when convenient.

Data as of 17 Nov 2026, 02:07 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.15.3
Patch
Available – fixed in 4.2.0-RC.2, 4.1.12
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 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 thorsten phpMyFAQ to 4.2.0-RC.2 or 4.1.12.

Affected software

ProductAffectedFixed in
thorstenphpMyFAQAffected
  • >=4.2.0-alpha <4.2.0-RC.2
Fixed in
  • 4.2.0-RC.2
thorstenphpMyFAQAffected
  • <4.1.12
Fixed in
  • 4.1.12
PackagistphpMyFAQpkg:composer/phpMyFAQOther threatsAffected
  • <4.1.12
  • >=4.2.0-alpha <4.2.0-RC.2
Fixed in
  • 4.1.12
  • 4.2.0-RC.2

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

AI-suggested

This vulnerability is fixed in phpMyFAQ versions 4.1.12 and 4.2.0-RC.2. Users should upgrade to at least these versions to remediate the issue. No other mitigation is indicated.

Description

phpMyFAQ versions before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 have an information disclosure vulnerability. Unauthenticated attackers can access editor-only Private Notes by querying the public FAQ list API endpoints. This allows retrieval of internal remarks and ticket details from FAQs that are otherwise anonymously readable.

References

Community reviews

Loading reviews…