dbcve.org
VizairApplication · Radiometrics

CVE-2025-54863

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 2025-08 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Radiometrics VizAir is vulnerable to exposure of the system's REST API key through a publicly accessible configuration file. This allows attackers to remotely alter weather data and configurations, automate attacks against multiple instances, and extract sensitive meteorological data, which could potentially compromise airport operations. Additionally, attackers could flood the system with false alerts, leading to a denial-of-service condition and significant disruption to airport operations. Unauthorized remote control over aviation weather monitoring and data manipulation could result in incorrect flight planning and hazardous takeoff and landing conditions.

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 confidence

Radiometrics VizAir exposes the system's REST API key through a publicly accessible configuration file, allowing unauthenticated attackers to gain full administrative control over the aviation weather monitoring system and manipulate meteorological data.

MitigationImmediately rotate the exposed API key, restrict public access to configuration files via web server configuration, and conduct a thorough compromise assessment given the safety-critical nature of aviation weather systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VizairApplication
Affected:< 2025-08

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm VizAir installation and version
    Locate the VizAir installation directory or running process, then identify the installed version number. Compare against the affected range: versions before 2025-08 are vulnerable.
    Affected if VizAir is installed with a version earlier than 2025-08
  2. Locate the VizAir configuration file
    Identify the configuration file that stores REST API settings. Check the VizAir installation directory for config files (such as config.json, settings.xml, or similar) that may contain API credentials.
    Affected if A configuration file exists and contains a REST API key credential
  3. Verify web server configuration for config file access
    Examine the web server configuration (nginx.conf, Apache httpd.conf, or embedded server config) serving VizAir. Test whether the configuration file can be accessed via HTTP/HTTPS request from an untrusted network.
    Affected if The configuration file is accessible via a public web URL without authentication
  4. Inspect configuration file contents for exposed credentials
    Open the configuration file and verify if it contains an API key, token, or administrative credential in plaintext. Note the presence and value of any authentication secrets.
    Affected if The configuration file contains a plaintext API key or administrative credential
  5. Confirm the API key is active and unrestricted
    Attempt to use the discovered API key against VizAir REST API endpoints to verify it provides administrative access. Check if the API permits full administrative operations without additional authentication.
    Affected if The exposed API key grants full administrative access to the VizAir system

A user is affected if VizAir version is earlier than 2025-08 AND a configuration file containing a plaintext API key is accessible via the public web.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 2025-08 or later
Fixed in 2025-08
Interim mitigation

Immediately rotate the exposed API key, restrict public access to configuration files via web server configuration, and conduct a thorough compromise assessment given the safety-critical nature of aviation weather systems.

Fix this in Vizair Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54863 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54863 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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