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.
CVE-2026-63000
MEDIUMPre-NVD 6.46.4
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 6.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
6.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 6.4Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.4
- EG Score
- 6.4(low)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity64% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
Advisory Details (4)
Auto-updated Sep 23, 2026🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available
Version 5.21.2
Patch available: redaxo/core 5.21.2
https://github.com/redaxo/core/releases/tag/5.21.2github_commit Patch Available
commit a13abbffbad4 (redaxo/core)
Patch available: redaxo/core 5.21.2 (contains commit a13abbffbad4)
https://github.com/redaxo/core/commit/a13abbffbad4fdea46a4edc86cdba3335ca9e8f3github_pr Patch Available
fix: add missing CSRF protection to package update API
Patch available: redaxo/core 5.21.2 (PR #6579 merged 2026-06-29)
https://github.com/redaxo/core/pull/6579github Patch Available🟡 PoC Available
Missing CSRF Protection on Package Update Action Allows Forced Addon Updates · Advisory · redaxo/core · GitHub
https://github.com/redaxo/core/security/advisories/GHSA-m8r3-22v6-g877Vendor Advisories for CVE-2026-63000(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-23 15:17 UTCEG score recompute
- 2026-09-23 14:24 UTCEG score recompute
- 2026-09-23 14:24 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-63000?
CVE-2026-63000 is a medium vulnerability published on September 23, 2026. REDAXO is a PHP-based content management system. Prior to 5.21.2, rexapiinstallpackageupdate in redaxo/src/addons/install/lib/api/apipackageupdate.php inherits the false default from rexapifunction::requiresCsrfProtection() instead of requiring a CSRF token. An unauthenticated attacker can cause a…
When was CVE-2026-63000 disclosed?
CVE-2026-63000 was first published in the National Vulnerability Database on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-63000?
CVE-2026-63000 has a CVSS v3 base score of 6.4 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-63000?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63000, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63000
Is Your Infrastructure Affected by CVE-2026-63000?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.