vulnerability / NVI-00000800 / Revision 4
Craft CMS has a potential RCE with a compromised security key
OSV carries this publisher advisory for craftcms/cms, craftcms/cms. This is an aggregated source copy; consult the original publisher and compare update dates.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
Listed
CISA lists known exploitation. This does not establish exploitation of your system.
As of · CISA
8 HIGH (3.1)
security-advisories@github.com severity; no combined Null risk score.
8.1 HIGH (3.1)
nvd@nist.gov severity; no combined Null risk score.
21.642%
FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.97629. Missing scores are unknown.
As of · FIRST EPSS
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
craftcms/cms
source listedECOSYSTEM: introduced 5.0.0-RC1; fixed 5.5.8
### Impact This is an RCE vulnerability that affects Craft 4 and 5 installs where your security key has already been compromised. https://craftcms.com/knowledge-base/securing-craft#keep-your-secrets-secret Anyone running an unpatched version of Craft with a compromised security key is affected. ### Patches This has been patched in Craft 5.5.8 and 4.13.8. ### Workarounds If you can't update to a patched version, then rotating your security key and ensuring its privacy will help to migitgate the issue. ### References https://github.com/craftcms/cms/commit/e59e22b30c9dd39e5e2c7fe02c147bcbd004e603
craftcms/cms
source listedECOSYSTEM: introduced 4.0.0-RC1; fixed 4.13.8
### Impact This is an RCE vulnerability that affects Craft 4 and 5 installs where your security key has already been compromised. https://craftcms.com/knowledge-base/securing-craft#keep-your-secrets-secret Anyone running an unpatched version of Craft with a compromised security key is affected. ### Patches This has been patched in Craft 5.5.8 and 4.13.8. ### Workarounds If you can't update to a patched version, then rotating your security key and ensuring its privacy will help to migitgate the issue. ### References https://github.com/craftcms/cms/commit/e59e22b30c9dd39e5e2c7fe02c147bcbd004e603
Craft CMS Craft CMS
source listedThe linked source does not supply a complete affected-version range here.
CISA does not supply a complete application-specific affected range here. Follow the linked vendor advisory for version and configuration prerequisites.
03 / Response
What to do next
- vendor patch
The original advisory lists fixed boundaries 5.5.8 for craftcms/cms. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- vendor patch
The original advisory lists fixed boundaries 4.13.8 for craftcms/cms. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- investigate
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. CISA
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
- CISA catalog date-added and due-date fields are not the original vulnerability disclosure date or universal legal deadlines.
- NVD lastModified does not establish freshness of every associated CPE record.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-x684-96hh-833x ↗
GitHub Advisory Database via OSV · vendor advisory
Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.
- CVE-2025-23209 ↗
CISA · official catalog
Observed . CISA KEV; CC0 1.0. Catalog assertions are not evidence of customer compromise.
- CVE-2025-23209 ↗
NIST National Vulnerability Database · official catalog
Observed . This product uses data from the NVD API but is not endorsed or certified by the NVD.
- CVE-2025-23209 ↗
FIRST EPSS · official catalog
Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 4 ·
Source facts changed; compare the preserved prior revision.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.