# CVE-2021-33031: Missing authorization in n/a

> Attackers can modify other users' email addresses via the save API without proper authorization, potentially leading to account takeover.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 10 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vmf6-w6c6-596g

## What is CVE-2021-33031?

CVE-2021-33031 is a low-severity missing authorization vulnerability in n/a, published on 10 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In LabCup before <v2_next_18022, it is possible to use the save API to perform unauthorized actions for users without access to user management in order to, after successful exploitation, gain access to a victim's account. A user without the user-management privilege can change another user's email address if the attacker knows details of the victim such as the exact roles and group roles, ID, and remote authentication ID settings. These must be sent in a modified save API request. It was fixed in 6.3.0.03.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Labcup Labcup.

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

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

## Is CVE-2021-33031 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-33031 is a low-severity missing authorization vulnerability in n/a, published on 10 Jun 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-33031 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-33031/ (Markdown: https://insights.sbomify.com/CVE-2021-33031/index.md)
```

## Sources

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

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