dbcve.org
Camera StationApplication · Axis

CVE-2025-30026

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-11
Fix available
A fix is available. Upgrade to 5.58.47195 / 6.9.47069 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
The AXIS Camera Station Server had a flaw that allowed to bypass authentication that is normally required.

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 · moderate confidence

The AXIS Camera Station Server contained a vulnerability that allowed attackers to bypass the normal authentication mechanisms, potentially granting unauthorized access to the server without valid credentials. The critical CVSS score of 9.8 indicates this is easily exploitable over the network with no user interaction required.

MitigationOrganizations using AXIS Camera Station Server should immediately check for and apply any available security patches or updates from AXIS. Until a patch is obtained, network segmentation and restricting server access to trusted IPs should be considered as compensating controls.

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
Camera StationApplication
Affected:< 5.58.47195
Camera Station ProApplication
Affected:>= 6.0.25729, < 6.9.47069

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 if Axis Camera Station is installed
    On the Windows system running the server, open the Control Panel and navigate to Programs and Features. Look for entries named 'Axis Camera Station' or 'Axis Camera Station Pro' in the installed software list.
    Affected if Either product is found in the installed programs, proceed to version check.
  2. Check installed version of Axis Camera Station
    In the Programs and Features list, locate the Axis Camera Station entry and note the version number displayed in the Version column. Alternatively, launch the Axis Camera Station client, go to the Help menu, and select About to view the exact version number.
    Affected if The version is less than 5.58.47195 (for Axis Camera Station).
  3. Check installed version of Axis Camera Station Pro
    In the Programs and Features list, locate the Axis Camera Station Pro entry and note the version number displayed in the Version column. Alternatively, launch the Axis Camera Station Pro client, go to the Help menu, and select About to view the exact version number.
    Affected if The version is greater than or equal to 6.0.25729 and less than 6.9.47069.
  4. Verify server accessibility
    Check if the AXIS Camera Station Server service is running and accessible over the network on typical ports such as 5576 or 5577 used by the server for client connections.
    Affected if The server is running and exposed to network access, increasing the exploitability of this vulnerability.

A system is affected if Axis Camera Station is installed with a version below 5.58.47195, or Axis Camera Station Pro is installed with a version between 6.0.25729 and 6.9.47069 inclusive, and the server is network-accessible.

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 5.58.47195 / 6.9.47069 or later
Fixed in 5.58.471956.9.47069
Interim mitigation

Organizations using AXIS Camera Station Server should immediately check for and apply any available security patches or updates from AXIS. Until a patch is obtained, network segmentation and restricting server access to trusted IPs should be considered as compensating controls.

Recommended fix High confidence

Camera Station >= 5.58.47195 or Camera Station Pro >= 6.9.47069

  1. Identify the current AXIS Camera Station or Camera Station Pro version installed in the environment
  2. If running Camera Station, upgrade to version 5.58.47195 or later
  3. If running Camera Station Pro, upgrade to version 6.9.47069 or later
  4. After upgrading, verify the authentication mechanism is working correctly by attempting to access the server with valid credentials
  5. Confirm the server is no longer vulnerable by reviewing release notes or patch documentation for the new version

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

Fix this in Camera Station Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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