# CVE-2024-50945: Missing authorization in n/a

> Attackers can post product reviews without having purchased the item, compromising data integrity in SimplCommerce.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 18 Mar 2025
- **Also known as:** GHSA-567c-gxmx-3pq9

## What is CVE-2024-50945?

CVE-2024-50945 is a high-severity missing authorization 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

An improper access control vulnerability exists in SimplCommerce at commit 230310c8d7a0408569b292c5a805c459d47a1d8f, allowing users to submit reviews without verifying if they have purchased the product.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2024-50945 being exploited?

There is no known exploitation of CVE-2024-50945 in the wild and no public exploit code.

Public exploit code:

- SimplCommerce is affected by a Broken Access Control vulnerability in the review system, allowing unauthorized users to post reviews for products they have not purchased. (github_poc): https://github.com/AbdullahAlmutawa/CVE-2024-50945

## Fix prompt for AI coding agents

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

What it is: CVE-2024-50945 is a high-severity missing authorization 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: There is no known exploitation of CVE-2024-50945 in the wild and no public exploit code.

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-50945/ (Markdown: https://insights.sbomify.com/CVE-2024-50945/index.md)
```

## Sources

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

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