Stored XSS via unsanitized template names
Published Feb 14, 2024 · Updated Mar 13, 2025
Stored XSS in REDAXO 5.15.1 allows remote authenticated users to execute scripts in another user's browser through a template name. Template creation stores the Name field without sufficient sanitization, and the saved value is later emitted when an article uses that template. Template-management access is required, and execution begins when another user views the crafted page, exposing browser-session data and actions.
Summary
What happened
Stored XSS in REDAXO 5.15.1 allows remote authenticated users to execute scripts in another user's browser through a template name. Template creation stores the Name field without sufficient sanitization, and the saved value is later emitted when an article uses that template. Template-management access is required, and execution begins when another user views the crafted page, exposing browser-session data and actions.
The record
- CVE
- CVE-2024-25300
- Published
- Feb 14, 2024
- Updated
- Mar 13, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Feb 14, 2024CVE publishedPublication date reported by the CVE source.
- Mar 13, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- 2024 REDAXO CMS XSS proof of conceptproof of concept · demonstrated
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