Stored script execution via unescaped Copyright field
Published Mar 31, 2022 · Updated Aug 4, 2024
Stored XSS in HTMLy 2.8.1 allows remote authenticated users to execute script through the Copyright field on /admin/config. The saved Copyright value is rendered inside a span without neutralizing markup, so a payload can close the element and add an event-bearing body element. Administrator access is required to change the setting, and another user must interact with a page that renders the poisoned value.
Summary
What happened
Stored XSS in HTMLy 2.8.1 allows remote authenticated users to execute script through the Copyright field on /admin/config. The saved Copyright value is rendered inside a span without neutralizing markup, so a payload can close the element and add an event-bearing body element. Administrator access is required to change the setting, and another user must interact with a page that renders the poisoned value.
The record
- CVE
- CVE-2021-42946
- Published
- Mar 31, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 31, 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
- HAXSS HTMLy Copyright-field payloadproof 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