Stored XSS via unencoded blog title
Published Aug 3, 2021 · Updated Aug 4, 2024
Stored XSS in HTMLy 2.8.1 allows remote authenticated users to execute script in a visitor's browser through the blog title. The dashboard's admin/config handler stores the submitted site name, and page output renders that value without htmlentities encoding. Administrative access is required to change the title, and execution occurs when a visitor loads a page that renders the stored title.
Summary
What happened
Stored XSS in HTMLy 2.8.1 allows remote authenticated users to execute script in a visitor's browser through the blog title. The dashboard's admin/config handler stores the submitted site name, and page output renders that value without htmlentities encoding. Administrative access is required to change the title, and execution occurs when a visitor loads a page that renders the stored title.
The record
- CVE
- CVE-2021-36703
- Published
- Aug 3, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 3, 2021CVE 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
- HTMLy 2.8.1 persistent blog-title XSS proof of conceptproof 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