Stored XSS via forged privileged-user requests
Published Jan 16, 2025 · Updated Apr 28, 2026
Cross-site request forgery in starise Twitter Shortcode 0.9 and earlier allows remote attackers to store XSS payloads via forged requests. Patchstack has not published the vulnerable request handler or the precise validation operation omitted before persistent content is accepted. Successful exploitation requires a privileged user to act on attacker-controlled content, after which the stored payload can execute in browsers that render the affected site.
Summary
What happened
Cross-site request forgery in starise Twitter Shortcode 0.9 and earlier allows remote attackers to store XSS payloads via forged requests. Patchstack has not published the vulnerable request handler or the precise validation operation omitted before persistent content is accepted. Successful exploitation requires a privileged user to act on attacker-controlled content, after which the stored payload can execute in browsers that render the affected site.
The record
- CVE
- CVE-2025-23618
- Published
- Jan 16, 2025
- Updated
- Apr 28, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, CAPEC-592
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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