Craft Commerce has Stored XSS in Shipping Categories (Name & Description) Fields Leading to Potential Privilege Escalation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.2 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N · score source

EPSS

• CVE-2026-25485: 0.30% estimated exploitation activity in the next 30 days; percentile 22.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A stored XSS vulnerability in Craft Commerce allows attackers to execute malicious JavaScript in an administrator’s browser. This occurs because the Shipping Categories (Name & Description) fields in the Store Management section are not properly sanitized before being displayed in the admin panel. --- Proof of Concept Requirments - General permissions: - Access the control panel - Access Craft Commerce - Craft Commerce permissions: - Manage store settings - Manage shipping - An active administrator elevated session Steps to Reproduce 1. Log in to the Admin Panel with the attacker account with the permissions mentioned above. 2. Navigate to Commerce - Store Management - Shipping Categories (/admin/commerce/store-management/primary/shippingcategories). 3. Create a new shipping category. 4. In the Name field, enter the following payload: 4. Click Save & Go back to the previous page. 5. Notice the alert proving JavaScript execution. Privilege Escalation to Administrator: 1. Do…

Published by the source

2 Feb 2026, 22:45 UTC

Last modified by the source

3 Feb 2026, 21:40 UTC

Source last checked

26 Oct 2026, 14:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w8gw-qm8p-j9j3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25485

Advisory: Craft Commerce has Stored XSS in Shipping Categories (Name & Description) Fields Leading to Potential Privilege Escalation
IDs: CVE-2026-25485, GHSA-w8gw-qm8p-j9j3
Record: https://patchnext.com/advisories/cve-2026-25485 (revision 1, source checked 26 Oct 2026, 14:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: craftcms/composer 5.5.2, 4.10.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist craftcms/composer: affected >= 5.0.0-RC1, <= 5.5.1; >= 4.0.0-RC1, <= 4.10.0; fixed in 4.10.1, 5.5.2

## Suggested inspection (read-only)
- Packagist craftcms/composer: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on craftcms/composer.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w8gw-qm8p-j9j3 (GitHub-reviewed advisory GHSA-w8gw-qm8p-j9j3 lists affected ranges: Packagist craftcms/composer >=5.0.0-RC1 =4.0.0-RC1 <=4.10.0)

Commands are suggestions: review each one before running it.