How severe is CVE-2026-25491?

No CVSS score has been assigned to CVE-2026-25491 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-25491?

CVE-2026-25491 affects the following packages: craftcms/cms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-25491?

Update craftcms/cms to 5.8.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25491 is resolved across your whole dependency graph.

How do I detect CVE-2026-25491 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-25491 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2026-25491 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-25491 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-25491?

CVE-2026-25491 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-25491?

CVE-2026-25491 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-25491 published, and has it been updated?

CVE-2026-25491 was published on February 9, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2026-25491 — cms

Fix: craftcms/cms@cfd6ba0

CVE-2026-25491 is a Cross-site Scripting (XSS) vulnerability in craftcms/cms. A fix is available for craftcms/cms — see the affected versions and patch details below.

Craft has a Stored XSS in Entry Types Name

Also known asGHSA-7pr4-wx9w-mqwr

Published

Feb 9, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25491.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk-0.00%

Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘craftcms/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Stored XSS via Entry Type names. The name is not sanitized when displayed in the Entry Types list.

Proof of Concept

Required Permissions (Attacker)

Admin access (only admins have access to the settings page)
allowAdminChanges is enabled in production, which is against our security recommendations.

Steps to Reproduce

Log in as an attacker.
Go to Settings -> Entry Types (/admin/settings/entry-types).
Create a new Entry Type.
Set Name to:

<img src=x onerror="alert('XSS-EntryTypes')" hidden>

Save the Entry Type, and you’ll be redirected back to the entry types table automatically.
Notice the alert fires when the entry types table renders.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/cms`	≥ 5.0.0-RC1&&< 5.8.22	5.8.22`composer require craftcms/cms:^5.8.22`

Affected Products

1 product · 1 configurations

Application

craft cmscraftcms

≥ 5.0.0 && < 5.8.21

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update craftcms/cms to 5.8.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25491 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

## Summary Stored XSS via Entry Type names. The name is not sanitized when displayed in the Entry Types list. --- ## Proof of Concept ### Required Permissions (Attacker) - Admin access (only admins have access to the settings page) - `allowAdminChanges` is enabled in production, which is against our [security recommendations](https://craftcms.com/knowledge-base/securing-craft). ### Steps to Reproduce 1. Log in as an attacker. 2. Go to **Settings** -> **Entry Types** (`/admin/settings/entry-types`). 3. Create a new Entry Type. 4. Set **Name** to: ```html <img src=x onerror="alert('XSS-Entr

O3 Security · Impact-Aware SCA

Is CVE-2026-25491 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works