# CVE-2024-50653: Business logic in n/a

> Attackers can bypass coupon claim limits by sending repeated requests, allowing unlimited coupon collection in CRMEB.

- **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:** 15 Nov 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-f927-34r4-vxxw

## What is CVE-2024-50653?

CVE-2024-50653 is a high-severity vulnerability in n/a, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CRMEB <=5.4.0 is vulnerable to Incorrect Access Control. Users can bypass the front-end restriction of only being able to claim coupons once by capturing packets and sending a large number of data packets for coupon collection, achieving unlimited coupon collection.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Crmeb Crmeb.

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

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

## Is CVE-2024-50653 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-25763](https://insights.sbomify.com/CVE-2025-25763/): SQL injection in n/a (critical 9.8)
- [CVE-2023-30185](https://insights.sbomify.com/CVE-2023-30185/): File upload in n/a (critical 9.8)
- [CVE-2020-21787](https://insights.sbomify.com/CVE-2020-21787/): File upload in n/a (critical 9.8)
- [CVE-2020-25466](https://insights.sbomify.com/CVE-2020-25466/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-21394](https://insights.sbomify.com/CVE-2020-21394/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-50653 is a high-severity vulnerability in n/a, published on 15 Nov 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-50653 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-50653/ (Markdown: https://insights.sbomify.com/CVE-2024-50653/index.md)
```

## Sources

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

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