# CVE-2024-53476: Race condition in n/a

> Attackers can bypass inventory limits via race conditions, causing overselling and unfulfilled orders in SimplCommerce.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2024
- **Updated:** 28 Dec 2024
- **Also known as:** GHSA-jphx-whwm-8gpv

## What is CVE-2024-53476?

CVE-2024-53476 is a medium-severity vulnerability in n/a, published on 27 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A race condition vulnerability in SimplCommerce at commit 230310c8d7a0408569b292c5a805c459d47a1d8f allows attackers to bypass inventory restrictions by simultaneously submitting purchase requests from multiple accounts for the same product. This can lead to overselling when stock is limited, as the system fails to accurately track inventory under high concurrency, resulting in potential loss and unfulfilled orders.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2024-53476?


## How do I fix CVE-2024-53476?

No fix has been published for CVE-2024-53476 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-53476 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53476 exists.

Public exploit code:

- SimplCommerce is affected by a race condition vulnerability in the checkout logic, allowing multiple users to purchase more products than are in stock via simultaneous checkout requests. (github_poc): https://github.com/AbdullahAlmutawa/CVE-2024-53476

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53476 and fix it if it is affected.

What it is: CVE-2024-53476 is a medium-severity vulnerability in n/a, published on 27 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53476 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-53476/ (Markdown: https://insights.sbomify.com/CVE-2024-53476/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-53476
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-53476
- OSV: https://osv.dev/vulnerability/CVE-2024-53476

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-53476/
Summaries are generated and may contain mistakes; the official description above is the record.