Skip to main content
VulnerabilityPublished

CVE-2026-130342: thorsten phpMyFAQ · Insecure Direct Object Reference

Affects thorsten phpMyFAQSource CVE Database V5

0
Compare

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

Data as of 17 Nov 2026, 02:18 UTC

CVSS 4.0 base score
2.3Low
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.02.3
CNA (VulnCheck)CVSS 3.14.2
Patch
Available – fixed in 4.2.0-RC.2, 4.1.12
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/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

Upgrade phpMyFAQ to version 4.1.12 or later, or 4.2.0-RC.2 or later, where this issue is fixed. No other mitigation is indicated or necessary as the vulnerability is addressed by these official fixes.

Description

phpMyFAQ versions before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 have an authorization bypass vulnerability in multisite deployments. This flaw allows editors to delete attachment files belonging to other instances due to improper reference counting. The issue arises because linkedRecords() only counts local attachments, so deleting a shared attachment by its md5 hash causes File::delete() to remove the shared file, affecting other instances.

References

Community reviews

Loading reviews…