CVE-2026-111894
Deferred Deferred - Pending Action

Stored XSS in phpMyFAQ via iframe Injection in FAQ Content

Publication date: 2026-10-17

Last updated on: 2026-10-17

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-17
Last Modified
2026-10-17
Generated
2026-10-17
AI Q&A
2026-10-17
EPSS Evaluated
N/A
NVD
CVE-2026-111894
EUVD
EUVD-2026-103325

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
thorsten phpMyFAQ 3.2.1
thorsten phpMyFAQ 4.2.0-alpha

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a stored cross-site scripting (XSS) vulnerability in phpMyFAQ versions 3.2.1 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta. Authenticated content authors can inject JavaScript by embedding iframes with data:text/html sources in FAQ or News content. The application fails to properly sanitize input, allowing the malicious code to bypass security checks and execute when rendered via Twig's raw filter.

Detection Guidance

To detect this vulnerability, inspect phpMyFAQ FAQ or News entries for iframes with data:text/html sources. Check for entries containing <iframe src="data:text/html,<script> or similar patterns. Review Twig templates using the raw filter for unescaped output. Use browser developer tools to inspect rendered content for suspicious iframes or JavaScript execution.

Impact Analysis

Attackers can use this flaw to create phishing interfaces or redirect users to malicious sites by injecting JavaScript. This could lead to theft of sensitive data, session hijacking, or unauthorized actions performed on behalf of the user. The impact depends on user privileges and the content accessed.

Compliance Impact

This vulnerability could lead to data breaches, compromising personal or sensitive information. GDPR requires protection of personal data, and HIPAA mandates safeguards for health information. A successful exploit may violate compliance requirements, potentially resulting in legal penalties or reputational damage.

Mitigation Strategies

Immediately upgrade phpMyFAQ to versions 4.1.9 or later. Remove the data: scheme from allowed media and link schemes in the HTML sanitizer configuration. Restrict iframe sources to trusted hosts only. Add sandbox attributes to iframes or implement Content Security Policy headers to block unsafe data URIs. Review and remove any existing malicious FAQ or News entries containing data:text/html iframes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-111894. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart