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

> Authenticated low-privileged users can perform administrative actions and modify other users' data via unauthorized API calls in the Mitarbeiterportal.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 9 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-7r8m-v3x4-crwv

## What is CVE-2025-61075?

CVE-2025-61075 is a high-severity missing authorization vulnerability in n/a, published on 9 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple Incorrect Access Control vulnerabilities in adata Software GmbH Mitarbeiterportal 2.15.2.0 allow remote authenticated, low-privileged users to carry out administrative functions and manipulate data of other users via unauthorized API calls.

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

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

It affects 1 product.


Products: Adata Mitarbeiter Portal.

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

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

## Is CVE-2025-61075 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-61074](https://insights.sbomify.com/CVE-2025-61074/): Cross-site scripting in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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