REDAXO CMS is vulnerable to Reflected XSS in Mediapool Info Banner via args[types]
Published Nov 26, 2025 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
REDAXO CMS is vulnerable to Reflected XSS in Mediapool Info Banner via args[types]
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
A reflected Cross-Site Scripting (XSS) vulnerability exists in the Mediapool view where the request parameter args[types] is rendered into an info banner without HTML-escaping. This allows arbitrary JavaScript execution in the backend context when an authenticated user visits a crafted link while logged in.
Potential impact
Arbitrary JavaScript execution in the backend, enabling theft of session cookies, CSRF tokens, or other sensitive data, and allowing an attacker to perform any administrative actions on behalf of the affected user.
Technical context
Control Flow: 1. redaxo/src/addons/mediapool/pages/index.php reads args via rexrequest('args', 'array') and passes them through as $argUrl to media.list.php. 2. redaxo/src/addons/mediapool/pages/media.list.php injects $argUrl['args']['types'] into an HTML string without escaping:
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Nov 26, 2025 · Last refreshed Nov 3, 2026