Stored XSS via unsanitized 404 request metadata
Published Apr 5, 2021 · Updated Aug 3, 2024
Stored cross-site scripting in Joe Hoyle JH 404 Logger 1.1 and earlier allows remote attackers to execute JavaScript in an administrator's browser. The plugin stores attacker-controlled 404 URL paths and Referer header values, then renders them in its WordPress dashboard widget without sanitization or output encoding. No account is needed to plant a payload, but an authenticated administrator must open the dashboard widget to trigger it; execution occurs in that administrator's browser context.
Summary
What happened
Stored cross-site scripting in Joe Hoyle JH 404 Logger 1.1 and earlier allows remote attackers to execute JavaScript in an administrator's browser. The plugin stores attacker-controlled 404 URL paths and Referer header values, then renders them in its WordPress dashboard widget without sanitization or output encoding. No account is needed to plant a payload, but an authenticated administrator must open the dashboard widget to trigger it; execution occurs in that administrator's browser context.
The record
- CVE
- CVE-2021-24176
- Published
- Apr 5, 2021
- Updated
- Aug 3, 2024
- Vendor
- Joe Hoyle
- Product
- JH 404 Logger
- Classifications
- CWE-79, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 5, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.1 <=1.1
What conditions does exploitation require?
What is affected?
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
- WPScan curl proof of conceptproof of concept · validated
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