# CVE-2026-111906: phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta CSRF in Elasticsearch/OpenSearch Admin API Index Operations

> Attackers can trick admins into deleting search indexes or exhausting resources via CSRF in Elasticsearch/OpenSearch admin endpoints.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-4qjm-33q6-wmgj, GHSA-cmvh-fpmf-8gfx

## What is CVE-2026-111906?

CVE-2026-111906 is a high-severity vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta contains a cross-site request forgery vulnerability in the Elasticsearch and OpenSearch administration API endpoints, which do not validate a CSRF token for the create, drop, and import actions. Attackers can lure a user with CONFIGURATION_EDIT permission to a malicious page that triggers these actions, deleting search indexes, forcing re-indexing, or exhausting resources.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

No fix has been published for CVE-2026-111906 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111906 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111906 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111906 is a high-severity vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111906 exists.

Affected product: thorsten phpMyFAQ. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-111906/ (Markdown: https://insights.sbomify.com/CVE-2026-111906/index.md)
```

## Sources

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

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