Stored XSS via nonce-free settings submission
Published Jan 7, 2025 · Updated Apr 28, 2026
CSRF in the Instabot WordPress plugin 1.10 and earlier allows remote attackers to store malicious script through a forged settings request. Its settings form handlers accept submitted values without verifying a WordPress nonce, so attacker-controlled content is saved and later rendered. Exploitation requires a logged-in site user with access to the affected settings to visit attacker-controlled content; the stored JavaScript then executes in visitors' browsers.
Summary
What happened
CSRF in the Instabot WordPress plugin 1.10 and earlier allows remote attackers to store malicious script through a forged settings request. Its settings form handlers accept submitted values without verifying a WordPress nonce, so attacker-controlled content is saved and later rendered. Exploitation requires a logged-in site user with access to the affected settings to visit attacker-controlled content; the stored JavaScript then executes in visitors' browsers.
The record
- CVE
- CVE-2025-22571
- Published
- Jan 7, 2025
- Updated
- Apr 28, 2026
- Vendor
- Instabot
- Product
- Instabot
- Classifications
- CWE-352, CAPEC-62, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 7, 2025CVE 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.10 changes=[{"at":"1.11","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