Skip to main content
CVE-2026-130363VulnerabilityPublished

phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability that lets scoped

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130363· Medium 5.1

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

Data as of 17 Nov 2026, 04:51 UTC

CVSS 4.0 base score
5.1Medium
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.1
CNA (VulnCheck)CVSS 3.12.7
Patch
Available – fixed in 4.2.0-RC.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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 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 access to unpublished FAQ content. Avoid granting broad FAQ_EDIT rights to users who should not access drafts outside their scope. Follow vendor updates for official patches or temporary mitigations.

Description

phpMyFAQ versions from 4.2.0-alpha.2 up to but not including 4.2.0-RC.2 contain an authorization vulnerability. This flaw allows scoped editors to view draft FAQs outside their assigned categories or languages because the dashboard and admin search do not enforce category/language-scoped FAQ_EDIT permissions correctly. Authenticated editors can exploit this by loading the unpublished FAQs widget with a language parameter or querying the admin API to leak draft FAQ titles, IDs, and confirm words in draft bodies. The vulnerability has a low severity score of 2.7 and does not impact integrity or availability.

References

Community reviews

Loading reviews…