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

> Unauthenticated attackers can access arbitrary files on the system due to incorrect access control in the dynawebservice component.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-mhfx-j9x5-v427

## What is CVE-2025-52168?

CVE-2025-52168 is a medium-severity missing authorization vulnerability in n/a, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect access control in the dynawebservice component of agorum Software GmbH Agorum core open v11.9.2 & v11.10.1 allows unauthenticated attackers to access arbitrary files on the system.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-52168 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52168 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52168 is a medium-severity missing authorization vulnerability in n/a, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52168 exists.

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-52168/ (Markdown: https://insights.sbomify.com/CVE-2025-52168/index.md)
```

## Sources

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

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