CVE-2025-22961
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe GatesAir Maxiva UAXT and VAXT transmitters have an incorrect access control vulnerability in their web-based management interface. Unauthenticated attackers can directly access sensitive database backup files (snapshot_users.db) by navigating to publicly exposed URLs at /logs/devcfg/snapshot/ and /logs/devcfg/user/. This exposes sensitive user data including login credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the web interface is reachableIdentify the IP address or hostname of your GatesAir Maxiva UAXT or VAXT transmitter and verify the web-based management interface is accessible via HTTP/HTTPSAffected if The web interface is publicly accessible on the network
-
Test unauthenticated access to /logs/devcfg/snapshot/Using a web browser or curl command, navigate to http://[device-ip]/logs/devcfg/snapshot/ without providing any login credentialsAffected if The directory listing or the snapshot_users.db file loads without requiring authentication
-
Test unauthenticated access to /logs/devcfg/user/Using a web browser or curl command, navigate to http://[device-ip]/logs/devcfg/user/ without providing any login credentialsAffected if The directory or any backup files within it are accessible without authentication
-
Verify if snapshot_users.db is directly downloadableAttempt to directly access http://[device-ip]/logs/devcfg/snapshot/snapshot_users.db or similar paths to see if the database file can be downloadedAffected if The .db file downloads successfully without authentication prompts
Your environment is affected if the web management interface allows unauthenticated access to URLs under /logs/devcfg/snapshot/ or /logs/devcfg/user/, enabling download of the snapshot_users.db file containing user credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authentication and authorization controls on the /logs/devcfg/snapshot/ and /logs/devcfg/user/ directories, remove or secure the exposed backup files, and consider firmware update if available from GatesAir.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22961 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22961 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data