Stored XSS via forged privileged-user request
Published Nov 18, 2024 · Updated Apr 28, 2026
Cross-site request forgery in Suresh Kumar wp-login customizer 1.0 and earlier allows remote attackers to plant stored XSS. Patchstack identifies the outcome as stored XSS but does not disclose the vulnerable handler, request parameter, or missing request-verification operation. Exploitation requires a privileged user with an active WordPress session to interact with attacker-controlled content, after which the stored script runs in affected visitors' browsers.
Summary
What happened
Cross-site request forgery in Suresh Kumar wp-login customizer 1.0 and earlier allows remote attackers to plant stored XSS. Patchstack identifies the outcome as stored XSS but does not disclose the vulnerable handler, request parameter, or missing request-verification operation. Exploitation requires a privileged user with an active WordPress session to interact with attacker-controlled content, after which the stored script runs in affected visitors' browsers.
The record
- CVE
- CVE-2024-52424
- Published
- Nov 18, 2024
- Updated
- Apr 28, 2026
- Vendor
- Suresh Kumar
- Product
- wp-login customizer
- Classifications
- CWE-352, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 18, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record 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=0 <=1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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