Quick answers
- Is CVE-2026-111906 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111906 being exploited in the wild.
- How severe is CVE-2026-111906?
- Medium severity, with a CVSS score of 6.5, published 17 October 2026.
- Which products and versions are affected?
- Thorsten phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta.
- Is there a fix for CVE-2026-111906?
- Yes: fixed in phpMyFAQ 4.1.9, 4.2.0-beta. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111906 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-111906?
- Check whether you run Thorsten phpMyFAQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: phpMyFAQ 4.1.9, 4.2.0-beta
Technical details
The Elasticsearch and OpenSearch administration API endpoints in phpMyFAQ lack CSRF token validation on state-changing operations (create, drop, import). An attacker can craft a malicious page to trigger these actions against a user with CONFIGURATION_EDIT permission, requiring only network access and user interaction. This results in denial of service through index deletion or resource exhaustion, with a fix expected in versions 4.1.9 and 4.2.0-beta.
Affected products
- thorsten phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta
Timeline
- 2026-10-03: disclosed
- 2026-10-17: advisory