Forced token requests via missing nonce validation
Published Apr 15, 2024 · Updated Apr 28, 2026
CSRF in the Siteimprove WordPress plugin 2.0.6 and earlier allows remote attackers to trigger unwanted request-token actions. The request-token handler accepts a state-changing request without validating a WordPress nonce, allowing a forged request to run in a logged-in user's session. Exploitation requires a privileged user to visit a crafted page or link, and published sources do not identify the precise token-side effect.
Summary
What happened
CSRF in the Siteimprove WordPress plugin 2.0.6 and earlier allows remote attackers to trigger unwanted request-token actions. The request-token handler accepts a state-changing request without validating a WordPress nonce, allowing a forged request to run in a logged-in user's session. Exploitation requires a privileged user to visit a crafted page or link, and published sources do not identify the precise token-side effect.
The record
- CVE
- CVE-2024-32103
- Published
- Apr 15, 2024
- Updated
- Apr 28, 2026
- Vendor
- Siteimprove
- Product
- Siteimprove.ai
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 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=n/a <=2.0.6 changes=[{"at":"2.0.7","status":"unaffected"}]
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