CVE-2026-63000
Received Received - Intake

CSRF Bypass in REDAXO CMS Prior to 5.21.2

Vulnerability report for CVE-2026-63000, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-23

Last updated on: 2026-09-23

Assigner: GitHub, Inc.

Description

REDAXO is a PHP-based content management system. Prior to 5.21.2, rex_api_install_package_update in redaxo/src/addons/install/lib/api/api_package_update.php inherits the false default from rex_api_function::requiresCsrfProtection() instead of requiring a CSRF token. An unauthenticated attacker can cause a logged-in administrator's browser to request a selected package update from the configured REDAXO package server, changing installed addon code or disrupting the site without the administrator's intent. This issue is fixed in version 5.21.2.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-23
Last Modified
2026-09-23
Generated
2026-09-23
AI Q&A
2026-09-23
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
redaxo redaxo to 5.21.2 (exc)
redaxo redaxo 5.21.2

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-63000 is a CSRF (Cross-Site Request Forgery) vulnerability in the REDAXO CMS. The rex_api_install_package_update API function, which handles package updates, does not enforce CSRF protection. This allows an unauthenticated attacker to trick a logged-in administrator into silently triggering a package update via a malicious request. The vulnerability affects versions up to 5.21.1 and is patched in 5.21.2.

Detection Guidance

To detect this vulnerability, check the REDAXO version installed on your system. If it is below 5.21.2, the system is vulnerable. You can verify the version by inspecting the file redaxo/src/addons/install/lib/api/api_package_update.php and confirming the absence of the CSRF protection override in the rex_api_install_package_update class.

Impact Analysis

An attacker could force updates of addons, potentially enabling supply-chain attacks, downgrades to vulnerable versions, or disruption of the site. Since the request uses the admin's session cookie, it executes without further interaction, making it dangerous even for non-technical users.

Compliance Impact

This vulnerability could indirectly impact compliance with GDPR and HIPAA by enabling unauthorized changes to system components. An attacker could exploit the missing CSRF protection to force updates of addons, potentially introducing malicious code or downgrading to vulnerable versions. This may violate data integrity and security requirements under GDPR (e.g., Article 32) and HIPAA (e.g., Security Rule). Unauthorized modifications could also lead to unauthorized access or data breaches, further compromising compliance.

Mitigation Strategies

Immediately update REDAXO to version 5.21.2 or later to apply the CSRF protection fix. If immediate updating is not possible, manually add the missing CSRF protection by overriding the requiresCsrfProtection() method in redaxo/src/addons/install/lib/api/api_package_update.php to return true.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-63000. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart