CVE-2025-64050: redaxo · n/a
Affects redaxoSource CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubredaxo/redaxopkg:github/redaxo/redaxoOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately audit and restrict administrator access to the REDAXO CMS, enforcing strong authentication mechanisms such as multi-factor authentication (MFA). 2. Monitor template management activities and implement logging to detect unauthorized or suspicious changes to templates. 3. Isolate the CMS environment to limit potential lateral movement if compromise occurs, using network segmentation and strict firewall rules. 4. Regularly back up website data and templates to enable rapid recovery in case of compromise. 5. Apply principle of least privilege to all CMS users, ensuring only necessary personnel have administrative rights. 6. Stay informed on REDAXO CMS vendor communications for official patches or updates addressing this vulnerability and apply them promptly once available. 7. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious PHP code injections or unusual template modifications. 8. Conduct security awareness training for administrators to recognize phishing or social engineering attempts that could lead to credential compromise. 9. Perform regular vulnerability assessments and penetration testing focused on CMS components to identify and remediate weaknesses proactively.
Description
A Remote Code Execution (RCE) vulnerability in the template management component in REDAXO CMS 5.20.0 allows remote authenticated administrators to execute arbitrary operating system commands by injecting PHP code into an active template. The payload is executed when visitors access frontend pages using the compromised template.