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

> Low-privileged users can access read-only REST API endpoints to collect information due to missing authorization checks in Gatling Enterprise.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 6 Aug 2025
- **Updated:** 6 Aug 2025
- **Also known as:** GHSA-47xg-jggc-w6c4

## What is CVE-2025-51308?

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

### Official description

In Gatling Enterprise versions below 1.25.0, a low-privileged user that does not hold the role "admin" could perform a REST API call on read-only endpoints, allowing him to collect some information, due to missing authorization checks.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Gatling Gatling.

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

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

## Is CVE-2025-51308 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-51306](https://insights.sbomify.com/CVE-2025-51306/): Auth bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-51308 is a medium-severity missing authorization vulnerability in n/a, published on 6 Aug 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-51308 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-51308/ (Markdown: https://insights.sbomify.com/CVE-2025-51308/index.md)
```

## Sources

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

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