# CVE-2026-63000: REDAXO: Missing CSRF Protection on Package Update Action Allows Forced Addon Updates

> An unauthenticated attacker can force a logged-in administrator to update addons via CSRF, potentially altering site code or disrupting operations.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-m8r3-22v6-g877

## What is CVE-2026-63000?

CVE-2026-63000 is a medium-severity vulnerability in redaxo core, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-63000?

2 open source packages ship an affected version, including redaxo/source. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `redaxo/source` | Packagist | All versions | 5.21.2 |
| `redaxo/source` | Packagist | All versions | 5.21.2 |

Products: Redaxo Redaxo.

## How do I fix CVE-2026-63000?

Upgrade redaxo/source to 5.21.2 or later.

## Is CVE-2026-63000 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63000 exists.

## Other vulnerabilities in redaxo core

- [CVE-2018-18200](https://insights.sbomify.com/CVE-2018-18200/): SQL injection in n/a (critical 9.8)
- [CVE-2018-17831](https://insights.sbomify.com/CVE-2018-17831/): SQL injection in n/a (critical 9.8)
- [CVE-2026-21857](https://insights.sbomify.com/CVE-2026-21857/): Redaxo has Path Traversal in Backup Addon Leading to Arbitrary File Read (high 8.3)
- [CVE-2006-2843](https://insights.sbomify.com/CVE-2006-2843/): Code injection in n/a (high 7.5)
- [CVE-2006-2844](https://insights.sbomify.com/CVE-2006-2844/): Multiple PHP remote file inclusion vulnerabilities in Redaxo 3.0 allow remote attackers to execute arbitrary PHP code via a URL in the REX[I (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63000 and fix it if it is affected.

What it is: CVE-2026-63000 is a medium-severity vulnerability in redaxo core, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63000 exists.

Affected packages and fixed versions:
- redaxo/source (Packagist): affected all versions; fixed in 5.21.2
- redaxo/source (Packagist): affected all versions; fixed in 5.21.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63000/ (Markdown: https://insights.sbomify.com/CVE-2026-63000/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63000
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63000
- OSV: https://osv.dev/vulnerability/CVE-2026-63000

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63000/
Summaries are generated and may contain mistakes; the official description above is the record.