Stored XSS via forged privileged-user request
Published Nov 19, 2024 · Updated May 11, 2026
CSRF in the Hints Naver Blog WordPress plugin 1.0 and earlier allows remote attackers to plant stored XSS through a forged request. Neither the CNA record nor its referenced advisory identifies the affected request handler or the unvalidated field that stores script content. Exploitation requires a privileged user to visit a crafted page or submit a forged form, after which stored script can run in another user's browser.
Summary
What happened
CSRF in the Hints Naver Blog WordPress plugin 1.0 and earlier allows remote attackers to plant stored XSS through a forged request. Neither the CNA record nor its referenced advisory identifies the affected request handler or the unvalidated field that stores script content. Exploitation requires a privileged user to visit a crafted page or submit a forged form, after which stored script can run in another user's browser.
The record
- CVE
- CVE-2024-51639
- Published
- Nov 19, 2024
- Updated
- May 11, 2026
- Vendor
- NAVER Corporation
- Product
- Naver Blog
- Classifications
- CWE-352, CAPEC-592, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 19, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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