Stored XSS via unsanitized sitemap settings
Published Nov 1, 2021 · Updated Aug 3, 2024
Stored XSS in WP Sitemap Page before 1.7.0 allows remote authenticated users to execute script through crafted plugin settings. The Exclude pages setting stores markup without sufficient sanitization or output escaping and later renders it in an administrative view; older releases also expose the How to display the posts setting in back-end and front-end views. Administrator-level access is required to save a payload, and execution requires a user to load an affected administrative or sitemap view.
Summary
What happened
Stored XSS in WP Sitemap Page before 1.7.0 allows remote authenticated users to execute script through crafted plugin settings. The Exclude pages setting stores markup without sufficient sanitization or output escaping and later renders it in an administrative view; older releases also expose the How to display the posts setting in back-end and front-end views. Administrator-level access is required to save a payload, and execution requires a user to load an affected administrative or sitemap view.
The record
- CVE
- CVE-2021-24715
- Published
- Nov 1, 2021
- Updated
- Aug 3, 2024
- Vendor
- Tony Archambeau
- Product
- WP Sitemap Page
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Nov 1, 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.7.0 <1.7.0
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 settings-payload 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