# CVE-2025-22961: Information disclosure in n/a

> Unauthenticated attackers can access sensitive database backups containing user credentials via exposed URLs in GatesAir Maxiva transmitters.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Feb 2025
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-jrq6-48vf-qc9h

## What is CVE-2025-22961?

CVE-2025-22961 is a high-severity vulnerability in n/a, published on 13 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A critical information disclosure vulnerability exists in the web-based management interface of GatesAir Maxiva UAXT, VAXT transmitters due to Incorrect Access Control (CWE-284). Unauthenticated attackers can directly access sensitive database backup files (snapshot_users.db) via publicly exposed URLs (/logs/devcfg/snapshot/ and /logs/devcfg/user/). Exploiting this vulnerability allows retrieval of sensitive user data, including login credentials, potentially leading to full system compromise.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-22961 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22961 is a high-severity vulnerability in n/a, published on 13 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22961 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-22961/ (Markdown: https://insights.sbomify.com/CVE-2025-22961/index.md)
```

## Sources

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

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