Unauthorized STOMP messages via undisclosed CSRF bypass
Published Oct 16, 2025 · Updated Oct 16, 2025
Cross-site request forgery in affected Spring Framework releases allows remote attackers to send unauthorized STOMP messages over WebSocket. The flaw affects STOMP-over-WebSocket message authorization, but Spring has not disclosed the responsible class, method, or failed validation operation. Exploitation requires user interaction and a STOMP-over-WebSocket application; the reported consequence is unauthorized message submission.
Summary
What happened
Cross-site request forgery in affected Spring Framework releases allows remote attackers to send unauthorized STOMP messages over WebSocket. The flaw affects STOMP-over-WebSocket message authorization, but Spring has not disclosed the responsible class, method, or failed validation operation. Exploitation requires user interaction and a STOMP-over-WebSocket application; the reported consequence is unauthorized message submission.
The record
- CVE
- CVE-2025-41254
- Published
- Oct 16, 2025
- Updated
- Oct 16, 2025
- Vendor
- Spring
- Product
- Spring Framework
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2025CVE publishedPublication date reported by the CVE source.
- Oct 16, 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=5.3.x
- Affected versionversion=6.0.x
- Affected versionversion=6.1.x
- Affected versionversion=6.2.x
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