What is CVE-2024-29888?

CVE-2024-29888 is a medium-severity security vulnerability in saleor (pip), affecting versions >= 3.14.56, < 3.14.61. It is fixed in 3.14.61, 3.15.37, 3.16.34, 3.17.32, 3.18.28, 3.19.15.

How severe is CVE-2024-29888?

CVE-2024-29888 has a CVSS score of 4.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of saleor are affected by CVE-2024-29888?

saleor (pip) versions >= 3.14.56, < 3.14.61 is affected.

Is there a fix for CVE-2024-29888?

Yes. CVE-2024-29888 is fixed in 3.14.61, 3.15.37, 3.16.34, 3.17.32, 3.18.28, 3.19.15. Upgrade to this version or later.

Is CVE-2024-29888 exploitable, and should I be worried?

Whether CVE-2024-29888 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-29888 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2024-29888 in saleor

Q: How severe is CVE-2024-29888?

CVE-2024-29888 has a CVSS score of 4.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of saleor are affected by CVE-2024-29888?

saleor (pip) versions >= 3.14.56, < 3.14.61 is affected.

Q: Is there a fix for CVE-2024-29888?

Yes. CVE-2024-29888 is fixed in 3.14.61, 3.15.37, 3.16.34, 3.17.32, 3.18.28, 3.19.15. Upgrade to this version or later.

Q: Is CVE-2024-29888 exploitable, and should I be worried?

Whether CVE-2024-29888 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-29888 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-29888?

Upgrade: saleor to 3.14.61 or later, saleor to 3.15.37 or later, saleor to 3.16.34 or later, saleor to 3.17.32 or later, saleor to 3.18.28 or later, saleor to 3.19.15 or later.

Summary

Saleor: Customers' addresses leak when using Warehouse as a Pickup: Local stock only delivery method

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.

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

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

CVE-2024-29888 has a CVSS score of 4.2 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.14.61, 3.15.37, 3.16.34, 3.17.32, 3.18.28, 3.19.15); upgrading removes the vulnerable code path.

Affected versions

saleor (>= 3.14.56, < 3.14.61) saleor (>= 3.15.31, < 3.15.37) saleor (>= 3.16.27, < 3.16.34) saleor (>= 3.17.25, < 3.17.32) saleor (>= 3.18.19, < 3.18.28) saleor (>= 3.19.5, < 3.19.15)

Security releases

saleor → 3.14.61 (pip) saleor → 3.15.37 (pip) saleor → 3.16.34 (pip) saleor → 3.17.32 (pip) saleor → 3.18.28 (pip) saleor → 3.19.15 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

saleor to 3.14.61 or later; saleor to 3.15.37 or later; saleor to 3.16.34 or later; saleor to 3.17.32 or later; saleor to 3.18.28 or later; saleor to 3.19.15 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-29888? CVE-2024-29888 is a medium-severity security vulnerability in saleor (pip), affecting versions >= 3.14.56, < 3.14.61. It is fixed in 3.14.61, 3.15.37, 3.16.34, 3.17.32, 3.18.28, 3.19.15.
How severe is CVE-2024-29888? CVE-2024-29888 has a CVSS score of 4.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of saleor are affected by CVE-2024-29888? saleor (pip) versions >= 3.14.56, < 3.14.61 is affected.
Is there a fix for CVE-2024-29888? Yes. CVE-2024-29888 is fixed in 3.14.61, 3.15.37, 3.16.34, 3.17.32, 3.18.28, 3.19.15. Upgrade to this version or later.
Is CVE-2024-29888 exploitable, and should I be worried? Whether CVE-2024-29888 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-29888 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-29888?
- Upgrade saleor to 3.14.61 or later
- Upgrade saleor to 3.15.37 or later
- Upgrade saleor to 3.16.34 or later
- Upgrade saleor to 3.17.32 or later
- Upgrade saleor to 3.18.28 or later
- Upgrade saleor to 3.19.15 or later

Other vulnerabilities in saleor

CVE-IDSeverityPackage summary

CVE-2023-26051MediumSaleor: Saleor has Staff-Authenticated Error Message Information Disclosure Vulnerability via Python Exceptions CVE-2023-26052Lowsaleor: Saleor Unauthenticated Information Disclosure Vulnerability via Python Exceptions CVE-2019-13594Highsaleor: Mirumee Saleor CSRF Protection Disabled CVE-2022-0932Mediumsaleor: saleor Missing Authorization vulnerability CVE-2020-7964Mediumsaleor: Missing Authentication for Critical Function in Saleor