# CVE-2021-39409: Auth bypass in n/a

> Unauthenticated users can register as administrators, leading to privilege escalation and potential account takeover in the Online Student Rate System.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m35m-7rw2-qh2x

## What is CVE-2021-39409?

CVE-2021-39409 is a critical authentication bypass vulnerability in n/a, published on 24 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability exists in Online Student Rate System v1.0 that allows any user to register as an administrator without needing to be authenticated.

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

It affects 1 product.


Products: Online Student Rate System Project Online Student Rate System.

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

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

## Is CVE-2021-39409 being exploited?

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

Public exploit code:

- Admin account registration in Online Student Rate System (github_poc): https://github.com/StefanDorresteijn/CVE-2021-39409

## Other vulnerabilities in n/a

- [CVE-2021-39408](https://insights.sbomify.com/CVE-2021-39408/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-39409 is a critical authentication bypass vulnerability in n/a, published on 24 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-39409 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-39409/ (Markdown: https://insights.sbomify.com/CVE-2021-39409/index.md)
```

## Sources

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

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