# CVE-2025-50847: Cross-site request forgery in n/a

> Attackers can force users to add products to their comparison list via crafted requests, requiring user interaction.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 31 Jul 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-j927-gjfr-7859

## What is CVE-2025-50847?

CVE-2025-50847 is a medium-severity vulnerability in n/a, published on 31 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cross Site Request Forgery (CSRF) vulnerability in CS Cart 4.18.3, allows attackers to add products to a user's comparison list via a crafted HTTP request.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2025-50847?

It affects 1 product.


Products: Cs-Cart Cs-Cart.

## How do I fix CVE-2025-50847?

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

## Is CVE-2025-50847 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-2138](https://insights.sbomify.com/CVE-2017-2138/): Cross-site request forgery in CS-Cart Japanese Edition (high 8.8)
- [CVE-2016-4862](https://insights.sbomify.com/CVE-2016-4862/): Code injection in n/a (high 8.8)
- [CVE-2025-50850](https://insights.sbomify.com/CVE-2025-50850/): Auth bypass in n/a (high 8.6)
- [CVE-2009-4891](https://insights.sbomify.com/CVE-2009-4891/): SQL injection in n/a (high 7.5)
- [CVE-2008-6394](https://insights.sbomify.com/CVE-2008-6394/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-50847 and fix it if it is affected.

What it is: CVE-2025-50847 is a medium-severity vulnerability in n/a, published on 31 Jul 2025. 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-2025-50847 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-2025-50847/ (Markdown: https://insights.sbomify.com/CVE-2025-50847/index.md)
```

## Sources

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

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