Stored XSS via unsanitized blog tag names
Published Jan 19, 2022 · Updated Aug 4, 2024
Stored XSS in mysiteforme allows remote authenticated users to execute script through the blog-tag management interface. The POST /admin/blogTags/add handler accepts a script-bearing name and stores it without neutralization, so the tag page renders the input as executable markup. Authenticated management access is required to add the tag, and a later page view executes the payload in the viewer's browser context.
Summary
What happened
Stored XSS in mysiteforme allows remote authenticated users to execute script through the blog-tag management interface. The POST /admin/blogTags/add handler accepts a script-bearing name and stores it without neutralization, so the tag page renders the input as executable markup. Authenticated management access is required to add the tag, and a later page view executes the payload in the viewer's browser context.
The record
- CVE
- CVE-2021-46026
- Published
- Jan 19, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 19, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Stored blog-tag XSS request demonstrationproof of concept · demonstrated
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