Stored XSS via forged privileged-user requests
Published Oct 27, 2025 · Updated Oct 27, 2025
Cross-site request forgery in Reloadly Plugin 2.0.1 and earlier allows remote attackers to plant stored scripts through crafted requests. Patchstack has not disclosed the affected handler, request parameter, request-integrity check, or storage location used to persist the script. Exploitation requires a privileged user to act on attacker-controlled content, after which the stored script executes in the affected WordPress site context.
Summary
What happened
Cross-site request forgery in Reloadly Plugin 2.0.1 and earlier allows remote attackers to plant stored scripts through crafted requests. Patchstack has not disclosed the affected handler, request parameter, request-integrity check, or storage location used to persist the script. Exploitation requires a privileged user to act on attacker-controlled content, after which the stored script executes in the affected WordPress site context.
The record
- CVE
- CVE-2025-62956
- Published
- Oct 27, 2025
- Updated
- Oct 27, 2025
- Vendor
- Reloadly
- Product
- Reloadly Plugin
- Classifications
- CWE-352, CAPEC-592, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 27, 2025CVE publishedPublication date reported by the CVE source.
- Oct 27, 2025Record 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.1
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