GHSA-3vxg-x5f8-f5qf
Fix: craftcms/commerce@48a5d94GHSA-3vxg-x5f8-f5qf is a Information Exposure vulnerability in craftcms/commerce. O3 Security confirms whether GHSA-3vxg-x5f8-f5qf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Craft Commerce has an unauthenticated information disclosure that can leak some customer order data on anonymous payments
Real-World Exposure
craftcms/commerce🐘craftcms/commerceReal-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
PaymentsController::actionPay discloses some order data to unauthenticated users when an order number is provided and the email check fails during an anonymous payment.
The JSON error response includes the serialized order object (order), which contains some sensitive fields such as customer email, shipping address, and billing address.
Details
I manually audited frontend payment flows and found that actionPay() retrieves orders by number before authorization is fully enforced.
Code path:
- Load order by
number. - Evaluate whether payment is authorized for completed orders (
number + matching email). - If unauthorized, return failure.
- Failure response still includes
cartArray($order), which serializes sensitive order data.
Why is this a vulnerability?
- Authorization logic says the requester is not allowed to pay for a completed order without an email.
- But the response still returns the same completed order’s contents.
Impact
Type: Information Disclosure / Broken Access Control
Who is impacted:
- Any Commerce deployment where completed order numbers can be obtained or leaked.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | craftcms/commerce | ≥ 5.0.0&&< 5.6.0 | 5.6.0 |
| 🐘Packagist | craftcms/commerce | ≥ 4.0.0&&< 4.11.0 | 4.11.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/commerce. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update craftcms/commerce to 5.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3vxg-x5f8-f5qf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-3vxg-x5f8-f5qf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-3vxg-x5f8-f5qf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-3vxg-x5f8-f5qf in your dependencies?
O3 detects GHSA-3vxg-x5f8-f5qf across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.