Skip to main content
CVE-2026-130356VulnerabilityPublished

phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an authorization bypass that lets category- or

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130356· Medium 5.3

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

Data as of 17 Nov 2026, 05:04 UTC

CVSS 4.0 base score
5.3Medium
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.05.3
CNA (VulnCheck)CVSS 3.15.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: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 phpMyFAQ to 4.2.0-RC.2.

Affected software

ProductAffectedFixed in
thorstenphpMyFAQAffected
  • >=4.2.0-alpha.2 <4.2.0-RC.2
Fixed in
  • 4.2.0-RC.2
PackagistphpMyFAQpkg:composer/phpMyFAQOther threatsAffected
  • >=4.2.0-alpha.2 <4.2.0-RC.2
Fixed in
  • 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

If you cannot patch yet, restrict editor permissions carefully and monitor for suspicious faq/update requests targeting untranslated languages or unauthorized faqIds.

Description

A vulnerability in phpMyFAQ versions from 4.2.0-alpha.2 up to but not including 4.2.0-RC.2 allows an authorization bypass. This flaw enables category- or language-restricted editors to modify visibility ACLs and tags of any FAQ, including those they should not access. Attackers can exploit this by sending crafted faq/update requests with a target faqId and untranslated language code to expose restricted FAQs, remove tags, or overwrite orphaned FAQs.

References

Community reviews

Loading reviews…