# CVE-2024-45877: Missing authorization in n/a

> Low-privileged users can access all modules, manipulate other users' data, and change passwords due to incorrect access control in the user management function.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 13 Nov 2024
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-p972-2fg6-pw4j

## What is CVE-2024-45877?

CVE-2024-45877 is a medium-severity missing authorization vulnerability in n/a, published on 13 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

baltic-it TOPqw Webportal v1.35.283.2 is vulnerable to Incorrect Access Control in the User Management function in /Apps/TOPqw/BenutzerManagement.aspx. This allows a low privileged user to access all modules in the web portal, view and manipulate information and permissions of other users, lock other user or unlock the own account, change the password of other users, create new users or delete existing users and view, manipulate and delete reference data.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-45877?


## How do I fix CVE-2024-45877?

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

## Is CVE-2024-45877 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45877 and fix it if it is affected.

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

## Sources

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

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