# CVE-2026-111894: phpMyFAQ 3.2.1 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta Stored XSS via iframe data: URI

> Authenticated users can inject JavaScript via iframe data URIs in phpMyFAQ, enabling phishing or redirects for other viewers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-fg92-v5rr-4xjq, GHSA-wwmv-7qmx-vxv3

## What is CVE-2026-111894?

CVE-2026-111894 is a medium-severity cross-site scripting vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

phpMyFAQ 3.2.1 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta contains a stored cross-site scripting vulnerability that allows authenticated content authors to inject JavaScript by embedding iframes with data:text/html sources in FAQ or News content. Attackers can bypass the hostless media-host allowlist in FaqHelper::cleanUpContent(), which is rendered via Twig's raw filter, to run phishing interfaces or top-frame redirects for viewers.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-111894 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111894 is a medium-severity cross-site scripting vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. Any signed-in user can exploit it over the network, 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-111894 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-111894/ (Markdown: https://insights.sbomify.com/CVE-2026-111894/index.md)
```

## Sources

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

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