dbcve.org
Axis OsOperating system · Axis

CVE-2025-0360

HIGH · 7.8 CVSS v3.1 Published 2025-03-04
Fix available
A fix is available. Upgrade to 11.11.135 / 12.2.41 or later.
See remediation →
80/100
Remediation priority · High
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 could lead to an incorrect user privilege level in the VAPIX service account D-Bus API.

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 misconfiguration vulnerability exists in the VAPIX Device Configuration framework of Axis Communication devices. The flaw allows for an incorrect user privilege level to be assigned within the VAPIX service account D-Bus API, potentially enabling unauthorized access or actions beyond the intended permission boundaries.

MitigationApply the vendor-supplied firmware update for affected Axis devices that addresses the VAPIX Device Configuration framework privilege level issue.

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:>= 11.11.0, < 12.2.41
Axis Os 2024Operating system
Affected:< 11.11.135

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

CVSS:3.1/AV:L/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 Axis OS firmware version
    Access the device web interface and navigate to System > Overview, or query the VAPIX API endpoint /axis-cgi/sysinfo.cgi to retrieve the firmware version. Alternatively, check the device label or recovery interface.
    Affected if The installed version falls within >= 11.11.0 AND < 12.2.41, OR is < 11.11.135 for the 2024 release line.
  2. Confirm VAPIX service is accessible
    Verify the device has the VAPIX API enabled by attempting to access http://<device-ip>/axis-cgi/ or checking the device network configuration to confirm VAPIX ports (typically 80/443) are listening.
    Affected if VAPIX is exposed and accessible on the network, making the misconfigured D-Bus API reachable.
  3. Check VAPIX user account configuration
    Query the VAPIX D-Bus API or use the /axis-cgi/admin/ local user management interface to enumerate user accounts and their assigned privilege levels within the VAPIX service.
    Affected if A user account exists with an incorrect or elevated privilege level assigned through the VAPIX Device Configuration framework D-Bus API.
  4. Review VAPIX Device Configuration permissions
    Access the VAPIX Device Configuration settings page in the web interface (under Settings > VAPIX) or query the configuration API to review which user accounts have been granted device configuration privileges.
    Affected if A user account has been granted permissions beyond what was intended, indicating the privilege misconfiguration is present.

The device is affected if it runs Axis OS version 11.11.0 or higher but below 12.2.41 (or below 11.11.135 for 2024 releases) AND has VAPIX with user accounts configured through the Device Configuration framework.

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 11.11.135 / 12.2.41 or later
Fixed in 11.11.13512.2.41
Interim mitigation

Apply the vendor-supplied firmware update for affected Axis devices that addresses the VAPIX Device Configuration framework privilege level issue.

Recommended fix High confidence

Axis OS 12.2.41 (or later) / Axis OS 2024 11.11.135 (or later)

  1. 1. Identify the current Axis OS version by accessing the device web interface or using the VAPIX API
  2. 2. If running Axis OS 11.11.x (2024 branch), upgrade to version 11.11.135 or later
  3. 3. If running Axis OS 12.x, upgrade to version 12.2.41 or later
  4. 4. Before upgrading, backup the device configuration via the web interface or VAPIX
  5. 5. Apply the firmware upgrade through the Axis device manager or directly via the web interface
  6. 6. After upgrade, verify the device is operational and the VAPIX service account privilege level is correct
  7. 7. Confirm the fix by checking the Axis OS version matches or exceeds the fixed releases

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
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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