Quick answers
- Is CVE-2026-111894 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111894 being exploited in the wild.
- How severe is CVE-2026-111894?
- Medium severity, with a CVSS score of 5.4, published 17 October 2026.
- Which products and versions are affected?
- Thorsten phpMyFAQ 3.2.1 through 4.1.8; 4.2.0-alpha through 4.2.0-beta.
- Is there a fix for CVE-2026-111894?
- Yes: fixed in 4.1.9, 4.2.0-beta. Until then: Disable the iframe element and data: URI scheme in the HTML sanitizer configuration within FaqHelper::cleanUpContent() to prevent injection of hostless iframe payloads. Restrict FAQ and News content authoring permissions to trusted administrators only. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111894 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-111894?
- 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: 4.1.9, 4.2.0-beta
Disable the iframe element and data: URI scheme in the HTML sanitizer configuration within FaqHelper::cleanUpContent() to prevent injection of hostless iframe payloads. Restrict FAQ and News content authoring permissions to trusted administrators only.
Technical details
The vulnerability is a stored XSS flaw in phpMyFAQ's HTML sanitization configuration. The HTML sanitizer permits both iframe elements and data: URI schemes; because data: URLs contain no hostname, the configured media-host allowlist does not block them. An authenticated attacker can inject `<iframe src="data:text/html,<script>...</script>">` into FAQ or News content, which bypasses sanitization and is rendered via Twig's raw filter, causing arbitrary JavaScript execution in the victim's browser.
Affected products
- Thorsten phpMyFAQ 3.2.1 through 4.1.8; 4.2.0-alpha through 4.2.0-beta
Timeline
- 2026-10-03: disclosed
- 2026-10-17: advisory