CVE-2026-130356: thorsten phpMyFAQ · Insecure Direct Object Reference
Affects thorsten phpMyFAQSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.2.0-RC.2 when convenient.
Data as of 17 Nov 2026, 02:06 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 5.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.4 |
- Patch
- Available – fixed in 4.2.0-RC.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| thorstenphpMyFAQ | Affected
| Fixed in
|
PackagistphpMyFAQpkg:composer/phpMyFAQOther threats | Affected
| Fixed in
|
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.2.0-RC.2 or later, where this authorization bypass vulnerability has been fixed. No other mitigation is indicated by the vendor advisory.
Description
phpMyFAQ versions from 4.2.0-alpha.2 up to but not including 4.2.0-RC.2 contain an authorization bypass vulnerability. This flaw allows category- or language-restricted editors to modify visibility ACLs and tags of any FAQ by sending crafted update requests with specific faqId and untranslated language parameters. The vulnerability enables exposure of restricted FAQs, removal of tags, or overwriting of orphaned FAQs. The issue was fixed in version 4.2.0-RC.2.