Skip to main content
Menu
CVEs

CVE

thorsten/phpmyfaq cross-tenant configuration overwrite in Redis store

Only affects phpMyFAQ 4.2.0 pre-releases (4.2.0-alpha through 4.2.0-RC.1) on multisite setups where the master instance has Redis configuration storage enabled. Fixed in 4.2.0-RC.2.

CVE-2026-130351

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

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

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.2.0-RC.2
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Multisite setup where the master instance has Redis configuration storage enabled Tenants created through the instance add API inherit a copy of the master's configuration Affected pre-release versions of phpMyFAQ 4.2.0 (alpha through RC.2)

Published
Last modified
Reference
Last checked
25/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

phpMyFAQ has an authorization flaw in its multisite Redis configuration store, which is not limited to each tenant, so a tenant administrator can read and overwrite the main instance's configuration. Over the network, an attacker who needs high-privilege login and no action from anyone else can redirect the main instance's email (SMTP), set a known API token, or change its authentication settings.

Original description

phpMyFAQ from 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in the multisite Redis configuration store that is not tenant-scoped. As a result, tenant administrators can read and overwrite the master instance's effective configuration. Attackers can save configuration through /admin/api/configuration, optionally resetting storage.redisPrefix, to redirect master SMTP, set a known API token, or alter authentication settings.

Who should check

Teams running phpMyFAQ 4.2.0 pre-releases (alpha through RC.1) in multisite mode with master Redis configuration storage enabled.

“Affecting phpMyFAQ >= 4.2.0-alpha, < 4.2.0-RC.2”

vulncheck.com

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Packagist packages
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Multisite setup where the master instance has Redis configuration storage enabled Tenants created through the instance add API inherit a copy of the master's configuration Affected pre-release versions of phpMyFAQ 4.2.0 (alpha through RC.2)
  • Upgrade to a fixed version: 4.2.0-RC.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130351 (phpMyFAQ 4.2.0-alpha before 4.2.0-RC.2 Cross-Tenant Configuration Overwrite via Redis Store), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130351 (entry last updated 2026-11-17):
Affected:
- Packagist package thorsten/phpmyfaq: from 4.2.0-alpha, fixed in 4.2.0-RC.2
Fixed versions: 4.2.0-RC.2.
Conditions (all must be true for the bug to be hit):
- Multisite setup where the master instance has Redis configuration storage enabled (source: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6795-wmwp-422x)
- Tenants created through the instance add API inherit a copy of the master's configuration (source: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6795-wmwp-422x)
- Affected pre-release versions of phpMyFAQ 4.2.0 (alpha through RC.2) (source: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6795-wmwp-422x)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-130351 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130351 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6795-wmwp-422x
- https://github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2
- https://www.vulncheck.com/advisories/phpmyfaq-4.2.0-alpha-before-4.2.0-rc.2-cross-tenant-configuration-overwrite-via-redis-store
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130351
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130351"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Repository
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130351

Is CVE-2026-130351 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Each tenant created through the instance add API gets a copy of the master's configuration. A tenant administrator can read and overwrite the master's configuration, including redirecting master SMTP to an attacker relay and capturing master password-reset mail.Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-130351?

thorsten/phpmyfaq (Packagist): from 4.2.0-alpha before 4.2.0-RC.2.Source: cve.now feed data

Am I affected, and how do I check?

Affects pre-release versions of phpMyFAQ 4.2.0, from 4.2.0-alpha up to but not including 4.2.0-RC.2, on multisite setups where the master instance has Redis configuration storage enabled. Check the installed phpMyFAQ version and whether the master instance uses Redis for configuration storage.Source: github.com, vulncheck.com

How do I fix CVE-2026-130351?

Upgrade to phpMyFAQ 4.2.0-RC.2 or later, which is the listed fixed version. No workaround is listed in the facts.Source: github.com, vulncheck.com