# CVE-2021-3376: Privilege escalation in n/a

> Authenticated attackers can escalate privileges in Cuppa CMS by manipulating the user_group_id_field parameter in a POST request.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 14 Dec 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-wxm7-hj84-7p5w

## What is CVE-2021-3376?

CVE-2021-3376 is a high-severity vulnerability in n/a, published on 14 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Cuppa CMS Versions Before 31 Jan 2021 allows authenticated attackers to gain escalated privileges via a crafted POST request using the user_group_id_field parameter.

## Which versions are affected by CVE-2021-3376?

It affects 1 product.


Products: Cuppacms Cuppacms.

## How do I fix CVE-2021-3376?

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

## Is CVE-2021-3376 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-47990](https://insights.sbomify.com/CVE-2023-47990/): SQL injection in n/a (critical 9.8)
- [CVE-2023-39681](https://insights.sbomify.com/CVE-2023-39681/): Code injection in n/a (critical 9.8)
- [CVE-2022-38296](https://insights.sbomify.com/CVE-2022-38296/): File upload in n/a (critical 9.8)
- [CVE-2022-27984](https://insights.sbomify.com/CVE-2022-27984/): SQL injection in n/a (critical 9.8)
- [CVE-2022-27985](https://insights.sbomify.com/CVE-2022-27985/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3376 and fix it if it is affected.

What it is: CVE-2021-3376 is a high-severity vulnerability in n/a, published on 14 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-3376 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-2021-3376/ (Markdown: https://insights.sbomify.com/CVE-2021-3376/index.md)
```

## Sources

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

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