# REDAXO: Missing CSRF Protection on Package Update Action Allows Forced Addon Updates

Advisory record · `GHSA-m8r3-22v6-g877`

- **Identifiers:** `GHSA-m8r3-22v6-g877` · `CVE-2026-63000` · `PKSA-759m-q6p6-jn53`
- **State:** Confirmed
- **Severity:** CVSS 6.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 23 Sept 2026
- **Updated:** 23 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Sept 2026, 14:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `redaxo/source` (Packagist): affected `<5.21.2`; fixed in `5.21.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> REDAXO versions before 5.21.2 (Packagist redaxo/source) have a missing CSRF protection on the package update API action in the install addon, so the update endpoint does not require a CSRF check. An attacker would need to lure a logged-in administrator to a malicious page, which could then silently trigger an addon update from the package server; the source says this could enable disruption, or remote code execution if combined with a compromised package or a downgrade to a vulnerable version. Upgrade to redaxo/source 5.21.2, which contains the fix.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:L`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0015, the 4th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:55 UTC: First seen by agentprime
- 31 Oct 2026, 13:55 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m8r3-22v6-g877)

## Sources

- [GitHub Advisory Database: GHSA-m8r3-22v6-g877](https://github.com/advisories/GHSA-m8r3-22v6-g877)
- [OSV: GHSA-m8r3-22v6-g877](https://osv.dev/vulnerability/GHSA-m8r3-22v6-g877)
- <https://github.com/redaxo/core/security/advisories/GHSA-m8r3-22v6-g877>
- <https://github.com/redaxo/core/pull/6579>
- <https://github.com/redaxo/core/commit/a13abbffbad4fdea46a4edc86cdba3335ca9e8f3>
- <https://github.com/redaxo/core>
- <https://github.com/redaxo/core/releases/tag/5.21.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-m8r3-22v6-g877>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m8r3-22v6-g877/>. Everything for agents: <https://agentprime.io/llms.txt>.