CVE-2026-130341
Deferred Deferred - Pending Action

Stored XSS in phpMyFAQ via FAQ Comments

Vulnerability report for CVE-2026-130341, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-17

Last updated on: 2026-11-17

Assigner: VulnCheck

Description

phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains a stored cross-site scripting vulnerability that allows registered users to inject javascript: links via FAQ comments. When the comment editor is enabled, Utils::parseUrl() strips https:// from sanitized hrefs, turning an allowed https://javascript:443/ link into executable script that runs on the shared admin origin when clicked.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-17
Last Modified
2026-11-17
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 6 associated CPEs
Vendor Product Version / Range
phpmyfaq phpmyfaq to 4.1.12 (exc)
phpmyfaq phpmyfaq to 4.2.0-alpha (exc)
phpmyfaq phpmyfaq to 4.2.0-RC.2 (exc)
thorsten phpmyfaq to 4.1.12 (exc)
thorsten phpmyfaq to 4.2.0-alpha (exc)
thorsten phpmyfaq From 4.2.0-RC.2 (inc)

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 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2. It allows registered users to inject malicious JavaScript via FAQ comments when the comment editor is enabled. The Utils::parseUrl() function strips https:// from sanitized links, converting a seemingly safe https://javascript:443/ link into executable script that runs on the shared admin origin when clicked.

The vulnerability bypasses a previous fix by rewriting sanitized URLs into dangerous javascript: URLs. Exploitation requires the victim to click the malicious link, which can be disguised as a normal reference.

Detection Guidance

Check phpMyFAQ version with: grep -r 'phpMyFAQ' /var/www/ or similar paths. Inspect FAQ comments for suspicious javascript: links or unusual URLs. Review admin interface for unexpected scripts or unauthorized actions. Enable logging in phpMyFAQ to monitor comment submissions and URL modifications.

Impact Analysis

A successful attack allows attackers to execute arbitrary JavaScript in the context of the admin interface due to shared origin between frontend and admin pages. This can grant access to admin pages, CSRF tokens, and API calls. Attackers could steal sensitive data, perform unauthorized actions, or impersonate users.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. It may result in data breaches, unauthorized disclosures, or loss of control over personal data, potentially leading to regulatory penalties and compliance failures.

Mitigation Strategies

Upgrade phpMyFAQ to version 4.1.12 or 4.2.0-RC.2 or later immediately. Disable the comment editor feature if not required. Review and remove any existing malicious FAQ comments. Implement strict input validation for user-generated content. Monitor admin interfaces for unusual activity.

Chat Assistant

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

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...