CVE-2026-34729
Received Received - Intake
Stored XSS in phpMyFAQ Filter::removeAttributes() Before

Publication date: 2026-04-02

Last updated on: 2026-04-07

Assigner: GitHub, Inc.

Description
phpMyFAQ is an open source FAQ web application. Prior to version 4.1.1, there is a stored XSS vulnerability via Regex Bypass in Filter::removeAttributes(). This issue has been patched in version 4.1.1.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-02
Last Modified
2026-04-07
Generated
2026-05-06
AI Q&A
2026-04-02
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
phpmyfaq phpmyfaq to 4.1.1 (exc)
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 Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-34729 is a stored Cross-Site Scripting (XSS) vulnerability in the phpMyFAQ application versions up to 4.1.0. It arises from an insufficient sanitization mechanism in the Filter::removeAttributes() function, which uses a regex that only matches HTML attributes with double-quoted values. This allows attackers to bypass sanitization by submitting FAQ content containing single-quoted or unquoted dangerous HTML attributes, such as event handlers like onerror='alert(1)'. When this malicious content is rendered on the FAQ page, the embedded JavaScript executes in the browsers of users viewing the page.

The vulnerability requires an attacker to have authenticated admin privileges to insert the malicious payload, but it affects all users who view the FAQ page, enabling public XSS attacks.


How can this vulnerability impact me? :

This vulnerability can lead to several serious impacts including session hijacking, where attackers steal user sessions; phishing attacks by injecting malicious scripts; propagation of worms through self-replicating XSS that creates new FAQs containing the payload; and malware distribution via malicious redirects.

Because the malicious script executes in the context of the users' browsers who visit the FAQ page, it can compromise confidentiality and integrity of user data without affecting availability.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by checking if your phpMyFAQ installation is running a version prior to 4.1.1, as versions ≀ 4.1.0 are affected.

To detect exploitation attempts or presence of the vulnerability, you can search for FAQ content entries containing suspicious HTML attributes that use single quotes or unquoted event handlers such as onerror='...' or onerror=... which bypass the sanitization.

For example, you can query your database for FAQ entries containing these patterns using SQL commands like:

  • SELECT * FROM faq_content WHERE content LIKE "%onerror='%" OR content LIKE "%onerror=%";

Additionally, monitoring web server logs for requests that include suspicious payloads with event handler attributes in FAQ submissions by authenticated admin users may help detect attempts.


What immediate steps should I take to mitigate this vulnerability?

The immediate and recommended mitigation is to upgrade phpMyFAQ to version 4.1.1 or later, where the vulnerability has been patched by improving the attribute removal logic to handle single-quoted and unquoted attributes.

If upgrading immediately is not possible, restrict administrative access to trusted users only, as the vulnerability requires authenticated admin privileges to inject malicious payloads.

Additionally, review and sanitize existing FAQ content to remove any malicious event handler attributes that could trigger stored XSS.

Implement monitoring for suspicious FAQ content submissions and consider applying web application firewall (WAF) rules to block payloads containing event handler attributes with single or no quotes.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The stored Cross-Site Scripting (XSS) vulnerability in phpMyFAQ allows attackers with authenticated admin privileges to inject malicious scripts that execute in the browsers of users viewing the FAQ page. This can lead to session hijacking, phishing, malware distribution, and worm propagation.

Such impacts can compromise the confidentiality and integrity of user data, potentially violating data protection requirements under standards like GDPR and HIPAA, which mandate safeguarding personal and sensitive information against unauthorized access and attacks.

Therefore, if exploited, this vulnerability could lead to non-compliance with these regulations due to the risk of unauthorized data exposure and manipulation.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart