# CVE-2026-25483: Craft Commerce has Stored XSS via Order Status Message with potential database exfiltration

> Stored XSS in Craft Commerce allows attackers to execute scripts and potentially exfiltrate sensitive database information including credentials and PII.

- **Severity:** Medium 6.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-8478-rmjg-mjj5

## What is CVE-2026-25483?

CVE-2026-25483 is a medium-severity cross-site scripting vulnerability in craftcms commerce, published on 3 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Craft Commerce is an ecommerce platform for Craft CMS. In versions from 4.0.0-RC1 to 4.10.0 and from 5.0.0 to 5.5.1, a stored XSS vulnerability exists in Craft Commerce’s Order Status History Message. The message is rendered using the |md filter, which permits raw HTML, enabling malicious script execution. If a user has database backup utility permissions (which do not require an elevated session), an attacker can exfiltrate the entire database, including all user credentials, customer PII, order history, and 2FA recovery codes. This issue has been patched in versions 4.10.1 and 5.5.2.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-25483?

4 open source packages ship an affected version, including craftcms/commerce. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `craftcms/commerce` | Packagist | From 4.0.0-RC1 | 4.10.1 |
| `craftcms/commerce` | Packagist | From 4.0.0-RC1 | 4.10.1 |
| `craftcms/commerce` | Packagist | From 5.0.0 | 5.5.2 |
| `craftcms/commerce` | Packagist | From 5.0.0 | 5.5.2 |

Products: Craftcms Craft Commerce.

## How do I fix CVE-2026-25483?

Upgrade craftcms/commerce to a fixed version for your release line: 4.10.1 or 5.5.2.

## Is CVE-2026-25483 being exploited?

There is no known exploitation of CVE-2026-25483 in the wild and no public exploit code.

## Other vulnerabilities in craftcms commerce

- [CVE-2026-29172](https://insights.sbomify.com/CVE-2026-29172/): Craft Commerce has a SQL Injection in Commerce Purchasables Table Sorting (high 8.7)
- [CVE-2026-29174](https://insights.sbomify.com/CVE-2026-29174/): Craft Commerce has a SQL Injection in Commerce Inventory Table Sorting (high 8.7)
- [CVE-2026-29175](https://insights.sbomify.com/CVE-2026-29175/): Multiple Stored XSS in Commerce Inventory Page Leading to Session Hijacking (high 8.6)
- [CVE-2026-31867](https://insights.sbomify.com/CVE-2026-31867/): Craft Commerce has a Potential IDOR in Commerce carts (medium 6.3)
- [CVE-2026-25482](https://insights.sbomify.com/CVE-2026-25482/): Craft Commerce has Stored DOM XSS in Order Status Name (Reflects in "Recent Orders" Dashboard Widget) (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25483 and fix it if it is affected.

What it is: CVE-2026-25483 is a medium-severity cross-site scripting vulnerability in craftcms commerce, published on 3 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-25483 in the wild and no public exploit code.

Affected packages and fixed versions:
- craftcms/commerce (Packagist): affected from 4.0.0-RC1; fixed in 4.10.1
- craftcms/commerce (Packagist): affected from 4.0.0-RC1; fixed in 4.10.1
- craftcms/commerce (Packagist): affected from 5.0.0; fixed in 5.5.2
- craftcms/commerce (Packagist): affected from 5.0.0; fixed in 5.5.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25483/ (Markdown: https://insights.sbomify.com/CVE-2026-25483/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25483
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25483
- OSV: https://osv.dev/vulnerability/CVE-2026-25483

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25483/
Summaries are generated and may contain mistakes; the official description above is the record.