Forced addon updates via missing CSRF check
Published Sep 23, 2026 · Updated Sep 23, 2026
CSRF in REDAXO Core 5.21.1 and earlier allows remote attackers to force addon updates through a logged-in administrator's browser. The rex_api_install_package_update action inherits the base class's false requiresCsrfProtection() default, so it accepts update requests without a CSRF token. Exploitation requires an administrator to visit attacker-controlled content; the resulting request can replace installed addon code or disrupt the site.
Summary
What happened
CSRF in REDAXO Core 5.21.1 and earlier allows remote attackers to force addon updates through a logged-in administrator's browser. The rex_api_install_package_update action inherits the base class's false requiresCsrfProtection() default, so it accepts update requests without a CSRF token. Exploitation requires an administrator to visit attacker-controlled content; the resulting request can replace installed addon code or disrupt the site.
The record
- CVE
- CVE-2026-63000
- Published
- Sep 23, 2026
- Updated
- Sep 23, 2026
- Vendor
- REDAXO
- Product
- REDAXO Core
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 2026CVE publishedPublication date reported by the CVE source.
- Sep 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.21.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- GHSA-m8r3-22v6-g877 CSRF proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started