Stored XSS via forged settings update
Published Sep 13, 2021 · Updated Aug 3, 2024
Cross-site request forgery in Evona Per Page Add to Head before 1.4.4 allows remote attackers to store script-bearing HTML. The admin settings endpoint accepts a forged POST without a CSRF check and stores the submitted HTML for later page rendering. Exploitation requires a logged-in administrator to submit the forged form; the payload then executes in administrator or site visitors' browsers.
Summary
What happened
Cross-site request forgery in Evona Per Page Add to Head before 1.4.4 allows remote attackers to store script-bearing HTML. The admin settings endpoint accepts a forged POST without a CSRF check and stores the submitted HTML for later page rendering. Exploitation requires a logged-in administrator to submit the forged form; the payload then executes in administrator or site visitors' browsers.
The record
- CVE
- CVE-2021-24586
- Published
- Sep 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Evona
- Product
- Per Page Add to Head
- Classifications
- CWE-352, CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 13, 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.4.4 <1.4.4
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 forged settings form 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