How severe is CVE-2026-31887?

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

Which packages are affected by CVE-2026-31887?

CVE-2026-31887 affects the following packages: shopware/core (Packagist), shopware/core (Packagist), shopware/platform (Packagist), shopware/platform (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-31887?

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

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

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

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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

No public exploit code has been indexed for CVE-2026-31887 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-31887?

CVE-2026-31887 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th 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-31887?

CVE-2026-31887 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2026-31887 was published on March 11, 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-31887 — core

CVE-2026-31887 is a CWE-863 vulnerability in shopware/core. A fix is available for shopware/core — see the affected versions and patch details below.

Shopware unauthenticated data extraction possible through store-api.order endpoint

Also known asGHSA-7vvp-j573-5584

Published

Mar 11, 2026

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 9, 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-31887.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs20th percentile — riskier than 20% of all scored CVEsHighest risk

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

Real-World Exposure

4 pkgs affected

🐘shopware/core🐘shopware/core🐘shopware/platform🐘shopware/platform

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

An insufficient check on the filter types for unauthenticated customers allows access to orders of other customers. This is part of the deepLinkCode support on the store-api.order endpoint.

Details

Data Exposure

Depending on the order payload configuration, attackers may retrieve:

Customer names
Billing address
Shipping address
Email addresses
Ordered products
Order values
Order numbers
Order dates
Payment method information
Shipping method information
More customs, depending on the given associations in the request

Security Impact

This vulnerability allows:

Unauthorized access to foreign customer order data
Mass enumeration of recent orders
Potential scraping of customer personal information

Limitation

No limitation, but only orders from the past 30 days are checked for changeable means of payment (unrelated).

Impact

The code is present since ~2021. Likely every version since then is impacted for every store.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`shopware/core`	≥ 6.7.0.0&&< 6.7.8.1	6.7.8.1`composer require shopware/core:^6.7.8.1`
🐘Packagist	`shopware/core`	all versions	6.6.10.15`composer require shopware/core:^6.6.10.15`
🐘Packagist	`shopware/platform`	≥ 6.7.0.0&&< 6.7.8.1	6.7.8.1`composer require shopware/platform:^6.7.8.1`
🐘Packagist	`shopware/platform`	all versions	6.6.10.15`composer require shopware/platform:^6.6.10.15`

Affected Products

1 product · 2 configurations

Application

shopwareshopware

≥ 6.7.0.0 && < 6.7.8.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update shopware/core to 6.7.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-31887 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Summary An insufficient check on the filter types for unauthenticated customers allows access to orders of other customers. This is part of the `deepLinkCode` support on the `store-api.order` endpoint. ### Details #### Data Exposure Depending on the order payload configuration, attackers may retrieve: - Customer names - Billing address - Shipping address - Email addresses - Ordered products - Order values - Order numbers - Order dates - Payment method information - Shipping method information - More customs, depending on the given associations in the request #### Security Impact This

O3 Security · Impact-Aware SCA

Is CVE-2026-31887 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works