# CVE-2026-130383: phpMyFAQ before 4.1.12 and 4.2.0-alpha.2 before 4.2.0-RC.2 Search Index Manipulation via solutionId


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/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-7jvq-w6ph-p3jq

## What is CVE-2026-130383?

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

### Official description

phpMyFAQ before 4.1.12 and 4.2.0-alpha.2 before 4.2.0-RC.2 contains an authorization bypass vulnerability that allows authenticated editors to manipulate search index documents by supplying an arbitrary solutionId to the /admin/api/faq/update endpoint. On Elasticsearch or OpenSearch deployments, category-restricted editors can remove published FAQs from search, overwrite other FAQs' search documents, or plant entries that remain searchable after unpublishing.

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

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

2 open source packages ship an affected version, including thorsten/phpmyfaq.


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

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

Upgrade thorsten/phpmyfaq to a fixed version for your release line: 4.1.12 or 4.2.0-RC.2.

## Is CVE-2026-130383 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- thorsten/phpmyfaq (Packagist): affected all versions; fixed in 4.1.12
- 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-130383/ (Markdown: https://insights.sbomify.com/CVE-2026-130383/index.md)
```

## Sources

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

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