# CVE-2026-130357: phpMyFAQ 4.2.0-alpha.2 before 4.2.0-RC.2 Privilege Escalation via updateUserRights


- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-r7gh-2w8p-p7q9

## What is CVE-2026-130357?

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

### Official description

phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an improper authorization vulnerability in updateUserRights that lets USER_EDIT admins drop category restrictions on group rights. Attackers can re-save rights through the user update-rights API to convert category-restricted group rights into global direct rights, then edit, publish or delete FAQs in withheld categories.

Weakness: CWE-863 (Incorrect Authorization)

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

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.2 | 4.2.0-RC.2 |

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

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

## Is CVE-2026-130357 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- thorsten/phpmyfaq (Packagist): affected from 4.2.0-alpha.2; 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-130357/ (Markdown: https://insights.sbomify.com/CVE-2026-130357/index.md)
```

## Sources

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

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