dbcve.org
Axis OsOperating system · Axis

CVE-2025-0358

HIGH · 8.8 CVSS v3.1 Published 2025-06-02
Fix available
A fix is available. Upgrade to 12.4.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
During an annual penetration test conducted on behalf of Axis Communication, Truesec discovered a flaw in the VAPIX Device Configuration framework that allowed a privilege escalation, enabling a lower-privileged user to gain administrator privileges.

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

A privilege escalation vulnerability exists in the VAPIX Device Configuration framework of Axis Communication devices. The flaw allows an authenticated user with low-level privileges to elevate their access to administrator privileges, representing a vertical privilege escalation (CWE-269). This indicates a failure in role-based access control (RBAC) enforcement within the VAPIX authentication mechanism.

MitigationApply the vendor-supplied patch from Axis Communication immediately. Until patched, restrict network access to VAPIX management interfaces to trusted administrative IP addresses only and monitor for unauthorized privilege escalation attempts.

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
Axis OsOperating system
Affected:>= 12.0.0, < 12.4.0

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

CVSS:3.1/AV:N/AC:L/PR:L/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 the installed Axis OS version
    Access the device web interface and navigate to System > About, or use the VAPIX API endpoint /axis-cgi/admin/param.cgi?action=list&group=Properties.Firmware to retrieve the firmware version
    Affected if The reported version is >= 12.0.0 and < 12.4.0
  2. Confirm VAPIX Device Configuration is enabled
    Check if the VAPIX API is accessible by querying /axis-cgi/param.cgi?action=list, or verify in the device's network settings that VAPIX administration protocol is permitted
    Affected if VAPIX is accessible and allows API requests from network clients
  3. Verify existence of non-administrator user accounts
    Use the VAPIX API call /axis-cgi/admin/user.cgi?action=get or check the device user list via the web interface under Settings > Users
    Affected if There are one or more users with non-admin (viewer/operator) privileges configured on the device
  4. Check for administrative actions performed by non-admin users
    Review device system logs (accessible via /axis-cgi/admin/systemlog.cgi or the Log page in the web interface) for entries where userID references a non-administrator account performing administrative operations such as changing settings, modifying parameters, or altering user accounts
    Affected if Logs show non-admin users performing actions that should require administrator privileges

A user is affected if their Axis device runs Axis OS version 12.0.0 through 12.3.x, has VAPIX accessible, and has at least one non-administrator user account that could potentially perform administrative actions.

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 12.4.0 or later
Fixed in 12.4.0
Interim mitigation

Apply the vendor-supplied patch from Axis Communication immediately. Until patched, restrict network access to VAPIX management interfaces to trusted administrative IP addresses only and monitor for unauthorized privilege escalation attempts.

Recommended fix High confidence

Axis OS 12.4.0 or later

  1. 1. Identify the current Axis OS version by accessing the device web interface or using the VAPIX API (e.g., /opt/axis/bin/opticsysctrl -v or checking System > About in the GUI)
  2. 2. Confirm the installed version falls within the vulnerable range: >= 12.0.0 and < 12.4.0
  3. 3. Prior to upgrade, backup the device configuration through the web interface (System > Maintenance > Backup) or via VAPIX
  4. 4. Obtain the Axis OS 12.4.0 or later firmware from the official Axis download portal (www.axis.com) matching your specific device model
  5. 5. Upload and install the firmware upgrade through the device web interface (System > Maintenance > Upgrade) or via VAPIX /bin/firmware upgrade endpoint
  6. 6. After upgrade completes, verify the new version is >= 12.4.0
  7. 7. Confirm the vulnerability is resolved by attempting privilege escalation or verifying the VAPIX Device Configuration framework has been patched

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

Fix this in Axis Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
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,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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