Browser script execution via unsanitized login username
Published Oct 19, 2021 · Updated Aug 4, 2024
Reflected XSS in the Bludit 3.13.1 login page allows remote attackers to execute JavaScript in a user's browser via a crafted username. The admin/login page renders the supplied username as HTML without neutralizing event-handler markup, allowing an img onerror payload to run. Execution requires user interaction, and the resulting script runs in that user's browser context with access to page data available to scripts.
Summary
What happened
Reflected XSS in the Bludit 3.13.1 login page allows remote attackers to execute JavaScript in a user's browser via a crafted username. The admin/login page renders the supplied username as HTML without neutralizing event-handler markup, allowing an img onerror payload to run. Execution requires user interaction, and the resulting script runs in that user's browser context with access to page data available to scripts.
The record
- CVE
- CVE-2021-35323
- Published
- Oct 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 19, 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
- Bludit 3.13.1 login-page 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