How severe is GHSA-mrj3-f2h4-7w45?

GHSA-mrj3-f2h4-7w45 has a CVSS score of 4.2/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-mrj3-f2h4-7w45?

GHSA-mrj3-f2h4-7w45 affects the following packages: saleor (PyPI), saleor (PyPI), saleor (PyPI), saleor (PyPI), saleor (PyPI), saleor (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-mrj3-f2h4-7w45?

Update saleor to 3.14.61 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mrj3-f2h4-7w45 is resolved across your whole dependency graph.

How do I detect GHSA-mrj3-f2h4-7w45 in my PyPI dependencies?

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

How do I mitigate GHSA-mrj3-f2h4-7w45 if there is no patch (or I can't update yet)?

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.

Is GHSA-mrj3-f2h4-7w45 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mrj3-f2h4-7w45 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 GHSA-mrj3-f2h4-7w45?

GHSA-mrj3-f2h4-7w45 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 45th 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 GHSA-mrj3-f2h4-7w45?

GHSA-mrj3-f2h4-7w45 is classified as CWE-359 (CWE-359). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mrj3-f2h4-7w45 published, and has it been updated?

GHSA-mrj3-f2h4-7w45 was published on March 28, 2024 and was last updated on July 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.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

Saleor: Customers' addresses leak when using Warehouse as a `Pickup: Local stock only` delivery methodGHSA-mrj3-f2h4-7w45

MEDIUMFix: saleor/saleor#15697

GHSA-mrj3-f2h4-7w45 is a medium-severity (CVSS 4.2) CWE-359 vulnerability in saleor. A fix is available for saleor — see the affected versions and patch details below.

Also known asCVE-2024-29888PYSEC-2026-1890

Published

Mar 28, 2024

Updated

Jul 28, 2026

Affected

6 pkgs

Patched

6 / 6

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 GHSA-mrj3-f2h4-7w45.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected

🐍saleor🐍saleor🐍saleor🐍saleor🐍saleor🐍saleor

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

Description

Summary

Using Pickup: Local stock only as a click-and-collect points could cause a leak of customer addresses

Details

When using Pickup: Local stock only click-and-collect as a delivery method in specific conditions the customer could overwrite the warehouse address with its own, which exposes its address as click-and-collect address.

Impact

The vulnerability can cause the leak of customer's address when using click-and-collect delivery option marked as Local stock only. It has impact on all orders with click-and-collect delivery method marked as Pickup:Local stock only The affected versions: >=3.14.56 <3.14.61, >=3.15.31 <3.15.37, >=3.16.27 <3.16.34, >=3.17.25 <3.17.32, >=3.18.19 <3.18.28, >=3.19.5 <3.19.15 This issue has been patched in versions: 3.14.61, 3.15.37, 3.16.34, 3.17.32, 3.18.28, 3.19.15

Workaround

We strongly recommend upgrading to the latest versions, in case of inability to upgrade straight away, possible workarounds are:

turn off click-and-collect delivery method on warehouse view when Pickup option is set to Local stock only.
cherry-pick the changes from PRs: https://github.com/saleor/saleor/pull/15694 & https://github.com/saleor/saleor/pull/15697

References

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`saleor`	≥ 3.14.56&&< 3.14.61	3.14.61`pip install --upgrade 'saleor==3.14.61'`
🐍PyPI	`saleor`	≥ 3.15.31&&< 3.15.37	3.15.37`pip install --upgrade 'saleor==3.15.37'`
🐍PyPI	`saleor`	≥ 3.16.27&&< 3.16.34	3.16.34`pip install --upgrade 'saleor==3.16.34'`
🐍PyPI	`saleor`	≥ 3.17.25&&< 3.17.32	3.17.32`pip install --upgrade 'saleor==3.17.32'`
🐍PyPI	`saleor`	≥ 3.18.19&&< 3.18.28	3.18.28`pip install --upgrade 'saleor==3.18.28'`
🐍PyPI	`saleor`	≥ 3.19.5&&< 3.19.15	3.19.15`pip install --upgrade 'saleor==3.19.15'`

Affected Products

1 product · 6 configurations

Application

saleorsaleor

≥ 3.19.5 && < 3.19.15

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for saleor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update saleor to 3.14.61 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mrj3-f2h4-7w45 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.

Frequently Asked Questions

### Summary Using `Pickup: Local stock only` as a click-and-collect points could cause a leak of customer addresses ### Details When using `Pickup: Local stock only` click-and-collect as a delivery method in specific conditions the customer could overwrite the warehouse address with its own, which exposes its address as click-and-collect address. ### Impact The vulnerability can cause the leak of customer's address when using click-and-collect delivery option marked as `Local stock only`. It has impact on all orders with click-and-collect delivery method marked as `Pickup:Local stock only` T

O3 Security · Impact-Aware SCA

Is GHSA-mrj3-f2h4-7w45 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works