Quick answers
- Is CVE-2026-63000 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63000 being exploited in the wild.
- How severe is CVE-2026-63000?
- Medium severity, with a CVSS score of 6.4, published 23 September 2026.
- Which products and versions are affected?
- redaxo/source (Packagist) <= 5.21.1, ECOSYSTEM:introduced=0,fixed=5.21.2.
- Is there a fix for CVE-2026-63000?
- Yes. redaxo/source (Packagist): upgrade to 5.21.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63000 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-63000?
- Check whether you run redaxo/source (Packagist) or REDAXO at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- redaxo/source (Packagist): upgrade to 5.21.2 or later
composer require redaxo/source:^5.21.2
Technical details
The `rex_api_install_package_update` API function in REDAXO's install addon fails to override the `requiresCsrfProtection()` method, which defaults to `false` in the base `rex_api_function` class. An attacker can craft a CSRF attack (e.g., via an image tag on a malicious page) to trigger package updates when an authenticated admin visits the page. No user interaction beyond visiting the attacker's page is required, only that the admin remains logged into their REDAXO instance. The attack can force installation of specific add-on versions, creating a remote code execution vector if the targeted version contains vulnerabilities or has been compromised. The fix is straightforward: override `requiresCsrfProtection()` to return `true` in the vulnerable class, as other similar API functions already do.
Affected products
- REDAXO REDAXO
Identifiers
- CVE-2026-63000
- GHSA-m8r3-22v6-g877
Timeline
- 2026-09-23: disclosed