# CVE-2025-48024: Information disclosure in Checkmate

> Authenticated users can access sensitive application secrets via the settings API endpoint in BlueWave Checkmate.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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:** 15 May 2025
- **Updated:** 15 May 2025
- **Also known as:** GHSA-273c-54fq-2595, GHSA-jjmg-cjr4-439m

## What is CVE-2025-48024?

CVE-2025-48024 is a medium-severity vulnerability in BlueWave Checkmate, published on 15 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In BlueWave Checkmate before 2.1, an authenticated regular user can access sensitive application secrets via the /api/v1/settings endpoint.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2025-48024 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48024 is a medium-severity vulnerability in BlueWave Checkmate, published on 15 May 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-48024 in the wild and no public exploit code.

Affected product: BlueWave Checkmate. 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-48024/ (Markdown: https://insights.sbomify.com/CVE-2025-48024/index.md)
```

## Sources

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

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