CVE-2026-34729 | thorsten phpMyFAQ up to 4.1.0 Filter::removeAttributes cross site scripting (GHSA-cv2g-8cj8-vgc7)
VulDBArchived Apr 02, 2026✓ Full text saved
A vulnerability, which was classified as problematic , was found in thorsten phpMyFAQ up to 4.1.0 . The affected element is the function Filter::removeAttributes . The manipulation results in cross site scripting. This vulnerability was named CVE-2026-34729 . The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-354889 · CVE-2026-34729 · GHSA-CV2G-8CJ8-VGC7
THORSTEN PHPMYFAQ UP TO 4.1.0 FILTER::REMOVEATTRIBUTES CROSS SITE SCRIPTING
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.2 $0-$5k 0.08+
Summaryinfo
A vulnerability has been found in thorsten phpMyFAQ up to 4.1.0 and classified as problematic. The impacted element is the function Filter::removeAttributes. This manipulation causes cross site scripting. The identification of this vulnerability is CVE-2026-34729. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Detailsinfo
A vulnerability classified as problematic was found in thorsten phpMyFAQ up to 4.1.0. Affected by this vulnerability is the function Filter::removeAttributes. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-34729 since 03/30/2026. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
Upgrading to version 4.1.1 eliminates this vulnerability. The upgrade is hosted for download at github.com.
Productinfo
Type
Content Management System
Vendor
thorsten
Name
phpMyFAQ
Version
4.0
4.1.0
License
open-source
Website
Product: https://github.com/thorsten/phpMyFAQ/
CPE 2.3info
🔒
🔒
CPE 2.2info
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 4.2
VulDB Meta Temp Score: 4.2
VulDB Base Score: 2.4
VulDB Temp Score: 2.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.1
CNA Vector (GitHub_M): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Cross site scripting
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: phpMyFAQ 4.1.1
Timelineinfo
03/30/2026 CVE reserved
04/02/2026 +3 days Advisory disclosed
04/02/2026 +0 days VulDB entry created
04/02/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: GHSA-cv2g-8cj8-vgc7
Status: Confirmed
CVE: CVE-2026-34729 (🔒)
GCVE (CVE): GCVE-0-2026-34729
GCVE (VulDB): GCVE-100-354889
Entryinfo
Created: 04/02/2026 17:25
Changes: 04/02/2026 17:25 (67)
Complete: 🔍
Cache ID: 99:2F6:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸