dbcve.org
VizairApplication · Radiometrics

CVE-2025-61956

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 a lack of authentication mechanisms for critical functions, such as admin access and API requests. Attackers can modify configurations without authentication, potentially manipulating active runway settings and misleading air traffic control (ATC) and pilots. Additionally, manipulated meteorological data could mislead forecasters and ATC, causing inaccurate flight planning.

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 lacks authentication mechanisms for critical functions including admin access and API requests. This allows unauthenticated attackers to modify system configurations, manipulate active runway settings affecting ATC and pilots, and alter meteorological data used for forecasting and flight planning.

MitigationImplement robust authentication and authorization controls for all admin functions and API endpoints, combined with input validation and network segmentation to limit exposure of critical system interfaces.

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. Identify VizAir version
    Locate the VizAir installation and check the software version number. This is typically found in the About section of the web interface, in system logs, or in the installation directory metadata.
    Affected if The installed version is earlier than 2025-08 (e.g., 2025-07, 2025-06, or any version dated before August 2025).
  2. Test admin interface accessibility
    Attempt to access the administrative console or admin panel URL (commonly found at paths like /admin, /management, or a custom admin route specific to VizAir) without providing any credentials. Use a web browser or curl to send an unauthenticated HTTP request.
    Affected if The admin interface loads and allows access to configuration functions without requiring login credentials or session authentication.
  3. Test API endpoint accessibility
    Send unauthenticated HTTP requests to common API endpoints used by VizAir for runway configuration and meteorological data (typically /api/runways, /api/meteo, /api/config, or similar REST paths). Inspect the HTTP response code and content.
    Affected if API endpoints return data or accept modifications without requiring API keys, tokens, or any form of authentication.
  4. Assess network exposure
    Determine if the VizAir system is directly accessible from external networks or untrusted zones. Check firewall rules, VLAN placement, and whether the web interface is bound to public-facing IP addresses versus internal-only interfaces.
    Affected if The VizAir admin interface or API is reachable from networks outside the trusted internal network without network-level access controls.

If VizAir version is earlier than 2025-08 AND the admin panel or API endpoints are accessible without authentication from your network, the environment is affected by this vulnerability.

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.

dbcve · scoped
Upgrade available Upgrade to 2025-08 or later
Fixed in 2025-08
Interim mitigation

Implement robust authentication and authorization controls for all admin functions and API endpoints, combined with input validation and network segmentation to limit exposure of critical system interfaces.

Recommended fix Moderate confidence

VizAir version 2025-08 or later

  1. Identify the current installed version of Radiometrics VizAir
  2. Upgrade to VizAir version 2025-08 or later to remediate the missing authentication vulnerability
  3. After upgrading, verify that authentication is now required for admin access and API requests
  4. Test critical functions including configuration modifications, runway settings, and meteorological data handling to confirm proper authentication enforcement
  5. Review access logs after upgrade to ensure all administrative functions now require valid authentication credentials

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vizair Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
60.0 hours of engineering $10,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61956 — 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-61956 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