Stored XSS via unescaped action-log usernames
Published Jan 28, 2020 · Updated Aug 4, 2024
Stored XSS in Joomla! CMS 3.9.0 through 3.9.14 allows remote attackers to execute script through a crafted username in com_actionlogs. The component renders logged usernames without adequate output escaping, causing markup stored in a username to execute as active browser content. Execution requires another user to view the affected action log; the script then runs in that viewer's browser context and can read or alter page data.
Summary
What happened
Stored XSS in Joomla! CMS 3.9.0 through 3.9.14 allows remote attackers to execute script through a crafted username in com_actionlogs. The component renders logged usernames without adequate output escaping, causing markup stored in a username to execute as active browser content. Execution requires another user to view the affected action log; the script then runs in that viewer's browser context and can read or alter page data.
The record
- CVE
- CVE-2020-8421
- Published
- Jan 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 28, 2020CVE 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
No public exploit references are available in this record.
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