CVE-2026-63000 redaxo CVE debrief

Who should care

Defenders responsible for REDAXO installations should assess exposure and apply the patch from version 5.21.2 if necessary. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure and apply the patch to prevent potential disruptions or code changes.

Why it matters

Defenders should prioritize verifying exposure of REDAXO installations to this CSRF vulnerability and apply the patch from version 5.21.2 if necessary. This issue allows an unauthenticated attacker to cause a logged-in administrator's browser to request a selected package update, potentially changing installed addon code or disrupting the site.

• An unauthenticated attacker can cause a logged-in administrator's browser to request a selected package update
• Installed addon code can be changed or the site disrupted without the administrator's intent

Technical summary

The rex_api_install_package_update function in REDAXO versions prior to 5.21.2 inherits the false default from rex_api_function::requiresCsrfProtection() instead of requiring a CSRF token. This allows an unauthenticated attacker to cause a logged-in administrator's browser to request a selected package update, potentially changing installed addon code or disrupting the site without the administrator's intent. The issue is fixed in version 5.21.2 and defenders should prioritize verifying exposure of REDAXO installations to this CSRF vulnerability and apply the patch from version 5.21.2 if necessary.

Defensive priority

Defenders should prioritize verifying exposure of REDAXO installations to this CSRF vulnerability and apply the patch from version 5.21.2 if necessary.

Recommended defensive actions

• Verify REDAXO installation version and exposure to this vulnerability
• Apply patch from version 5.21.2 if REDAXO installation is vulnerable
• Monitor for unusual package update requests
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the CSRF vulnerability in REDAXO versions prior to 5.21.2. The issue allows an unauthenticated attacker to cause a logged-in administrator's browser to request a selected package update.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.