# CVE-2026-130351: phpMyFAQ 4.2.0-alpha before 4.2.0-RC.2 Cross-Tenant Configuration Overwrite via Redis Store


- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-vmcw-7j96-cwc5

## What is CVE-2026-130351?

CVE-2026-130351 is a high-severity vulnerability in thorsten phpMyFAQ, published on 17 Nov 2026. 

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

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

1 open source package ship an affected version, including thorsten/phpmyfaq.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `thorsten/phpmyfaq` | Packagist | `pkg:composer/thorsten/phpmyfaq` | From 4.2.0-alpha | 4.2.0-RC.2 |

## How do I fix CVE-2026-130351?

Upgrade thorsten/phpmyfaq to 4.2.0-RC.2 or later.

## Is CVE-2026-130351 being exploited?

There is no known exploitation of CVE-2026-130351 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130351 and fix it if it is affected.

What it is: CVE-2026-130351 is a high-severity vulnerability in thorsten phpMyFAQ, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130351 in the wild and no public exploit code.

Affected packages and fixed versions:
- thorsten/phpmyfaq (Packagist): affected from 4.2.0-alpha; fixed in 4.2.0-RC.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130351/ (Markdown: https://insights.sbomify.com/CVE-2026-130351/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130351
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130351
- OSV: https://osv.dev/vulnerability/CVE-2026-130351

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130351/
Summaries are generated and may contain mistakes; the official description above is the record.
