Stored XSS via forged privileged requests
Published Jun 27, 2025 · Updated Apr 28, 2026
Cross-site request forgery in Dmytro O. Redchuk re.place 0.2.1 and earlier allows remote attackers to store XSS via crafted requests. The public record identifies stored XSS as the resulting action but does not disclose the affected handler or its missing request-authenticity check. Exploitation requires a privileged user with an active WordPress session to visit attacker-controlled content; the stored script then executes for later viewers.
Summary
What happened
Cross-site request forgery in Dmytro O. Redchuk re.place 0.2.1 and earlier allows remote attackers to store XSS via crafted requests. The public record identifies stored XSS as the resulting action but does not disclose the affected handler or its missing request-authenticity check. Exploitation requires a privileged user with an active WordPress session to visit attacker-controlled content; the stored script then executes for later viewers.
The record
- CVE
- CVE-2025-53338
- Published
- Jun 27, 2025
- Updated
- Apr 28, 2026
- Vendor
- Dmytro O. Redchuk
- Product
- re.place
- Classifications
- CWE-352, CAPEC-592, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 27, 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 <=0.2.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