REDAXO 5.21.2 Fixes CSRF and Stored XSS Flaws
Tech GuruQuick Answer
REDAXO 5.21.2 fixes two stored cross-site scripting flaws and a missing anti-forgery check on addon updates. Earlier releases through 5.21.1 are listed as affected. These are backend and media-management risks, not evidence that every visitor can take over every REDAXO site.
Confirm Scope And Apply The Supported Fix
Next step: Back up the site and database, confirm addon compatibility, and install the fixed core release. Review who can modify Media Manager types, place files in the media directory, and perform package updates.
Last verified: 2026-09-23 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | REDAXO releases through 5.21.1 |
|---|---|
| Advisory | GHSA-mf2p-wjp4-99pq / GHSA-w998-qmw9-mf4m / GHSA-m8r3-22v6-g877 |
| CVEs | CVE-2026-63000, CVE-2026-63001, CVE-2026-63002 |
| Authoritative release date | 2026-06-29 (publication date displayed by all three GitHub project advisories). |
| Authority revision date | No separate material revision date established in this review; all three advisories retrieved 2026-10-02. |
| Affected versions | REDAXO releases through 5.21.1 |
| Fixed version | REDAXO 5.21.2 |
| CVSS base score | 4.8 / 6.4 (CVSS v3.1) |
| CVSS severity | Medium |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
One flaw exposes administrators to unescaped Media Manager type names when deleting referenced media. Another renders filesystem filenames unsafely on the Mediapool sync page. The third can trick an authenticated administrator into an addon update because that action lacks CSRF protection. Their access and interaction requirements differ.
What To Validate Now
- Inventory. Locate REDAXO releases through 5.21.1 deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: REDAXO releases through 5.21.1 Do not infer applicability from product family or severity alone.
- Remediate. Apply REDAXO 5.21.2 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. On a staging copy, check media deletion warnings, media synchronization, and legitimate addon updates with the intended roles. Verify that untrusted names display as text and that update actions require the expected anti-forgery protection; preserve evidence before investigating suspicious existing entries.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
