Stored script execution via unescaped tag names
Published Dec 16, 2023 · Updated Aug 2, 2024
Stored XSS in phpMyFAQ before 3.1.17 allows remote authenticated users to execute script in another user's browser through a crafted tag. The admin tag autocomplete endpoint returned stored tag names without HTML-entity encoding, while the tag editor inserted edited values into span markup without escaping. An account able to create or edit tags is required, and execution occurs when another user loads or interacts with the affected tag interface, enabling actions and data access in that user's session.
Summary
What happened
Stored XSS in phpMyFAQ before 3.1.17 allows remote authenticated users to execute script in another user's browser through a crafted tag. The admin tag autocomplete endpoint returned stored tag names without HTML-entity encoding, while the tag editor inserted edited values into span markup without escaping. An account able to create or edit tags is required, and execution occurs when another user loads or interacts with the affected tag interface, enabling actions and data access in that user's session.
The record
- CVE
- CVE-2023-6889
- Published
- Dec 16, 2023
- Updated
- Aug 2, 2024
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 16, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <3.1.17
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Huntr bounty reproduction for stored tag XSSproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo