Skip to main content
VulnerabilityPublished

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

Affects thorsten phpMyFAQSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 4.2.0-RC.2 soon.

Data as of 17 Nov 2026, 02:05 UTC

CVSS 4.0 base score
7.1High
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.07.1
CNA (VulnCheck)CVSS 3.17.2
Patch
Available – fixed in 4.2.0-RC.2
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L

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.

Affected software

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

Upgrade phpMyFAQ to version 4.2.0-RC.2 or later, where this authorization bypass vulnerability has been fixed. No other mitigations are indicated by the vendor advisory.

Description

phpMyFAQ versions from 4.2.0-alpha up to but not including 4.2.0-RC.2 contain an authorization bypass vulnerability in the multisite Redis configuration store. This flaw allows tenant administrators to read and overwrite the master instance's configuration, including sensitive settings such as SMTP configuration, API tokens, and authentication parameters. The vulnerability arises because the Redis configuration store is not properly scoped per tenant, enabling unauthorized access to the master configuration.

References

Community reviews

Loading reviews…