# CVE-2025-50849: Missing authorization in n/a

> Authenticated users can modify other users' sticker settings by manipulating the company_id parameter due to missing server-side validation.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Jul 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-pp44-53wg-rwwx

## What is CVE-2025-50849?

CVE-2025-50849 is a high-severity missing authorization vulnerability in n/a, published on 31 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

CS Cart 4.18.3 is vulnerable to Insecure Direct Object Reference (IDOR). The user profile functionality allows enabling or disabling stickers through a parameter (company_id) sent in the request. However, this operation is not properly validated on the server side. An authenticated user can manipulate the request to target other users' accounts and toggle the sticker setting by modifying the company_id or other object identifiers.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-50849 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50849 is a high-severity missing authorization vulnerability in n/a, published on 31 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50849 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-50849/ (Markdown: https://insights.sbomify.com/CVE-2025-50849/index.md)
```

## Sources

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

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