Skip to main content
CVE-2025-0324VulnerabilityPublished

CVE-2025-0324: AXIS OS · Incomplete Filtering of Special Elements

Affects AXIS OSSource CVE Database V5

0

Not known to be exploited · CVSS 9.4 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Axis Communications AB AXIS OSAffected
  • =11.8.0
  • =12.0.0
Fixed in–

AI-suggested

European organizations should implement immediate compensating controls while awaiting official patches from Axis Communications. These include: 1) Restricting network access to AXIS OS devices by segmenting them into isolated VLANs or dedicated security zones with strict firewall rules limiting management interface exposure to trusted administrators only; 2) Enforcing strong authentication and access control policies on management interfaces, including multi-factor authentication where supported; 3) Monitoring network traffic and device logs for unusual configuration changes or access patterns indicative of privilege escalation attempts; 4) Applying network intrusion detection/prevention systems with signatures or heuristics tailored to Axis device protocols; 5) Conducting regular audits of device firmware versions and configurations to identify vulnerable devices; 6) Temporarily disabling or limiting remote management capabilities if not essential; and 7) Preparing incident response plans specific to surveillance device compromise. Organizations should prioritize patch deployment as soon as official updates become available and verify the integrity of firmware updates to prevent supply chain attacks.

Description

The VAPIX Device Configuration framework allowed a privilege escalation, enabling a lower-privileged user to gain administrator privileges.

References

Community reviews

Loading reviews…