What is the CVSS score of CVE-2025-30023?

CVE-2025-30023 has a CVSS 3.1 base score of 9.0 (Critical). CVSS vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 2.3%.

Which versions of Camera Station are affected by CVE-2025-30023?

CVE-2025-30023 is a critical remote code execution vulnerability affecting authenticated users of a client-server communication protocol, enabling arbitrary code execution that could compromise…. A patch is available.

How to fix or mitigate CVE-2025-30023?

Within 24 hours: identify all systems running affected client-server communication services and verify which versions are deployed; obtain vendor advisory to confirm exact product and affected version ranges. Within 7 days: deploy vendor-released patch to all identified systems in a staged rollout beginning with security-critical environments. Within 30 days: complete patching across all remaining systems and conduct post-patch validation to confirm successful remediation.

Camera Station CVE-2025-30023

EUVD-2025-21112 CRITICAL

Deserialization of Untrusted Data (CWE-502)

2025-07-11 product-security@axis.com

RCE Authentication Bypass Camera Station Device Manager Camera Station Pro

9.0

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.0 CRITICAL

AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack Vector

Adjacent

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 05:51 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

5.58,5.32,6.9

EUVD ID Assigned

Mar 16, 2026 - 08:17 euvd

EUVD-2025-21112

Analysis Generated

Mar 16, 2026 - 08:17 vuln.today

CVE Published

Jul 11, 2025 - 06:15 nvd

CRITICAL 9.0

DescriptionCVE.org

The communication protocol used between client and server had a flaw that could lead to an authenticated user performing a remote code execution attack.

AnalysisAI

CVE-2025-30023 is a critical remote code execution vulnerability in a client-server communication protocol that allows authenticated users to execute arbitrary code on affected systems. The flaw affects users with valid credentials who can access the affected service over an adjacent network segment, potentially compromising confidentiality, integrity, and availability across trust boundaries. While specific product details are limited in the provided data, this represents a high-severity risk requiring immediate patching, particularly if actively exploited or if public proof-of-concept code exists.

Technical ContextAI

This vulnerability is rooted in CWE-502 (Deserialization of Untrusted Data), indicating the communication protocol likely deserializes data without proper validation, allowing authenticated attackers to inject malicious payloads. The protocol appears to operate at the application layer between networked clients and servers. The flaw exists despite authentication requirements, suggesting the vulnerability bypasses or exploits trust assumptions in the authenticated communication channel. Without CPE data provided, the exact products affected cannot be determined; however, organizations should audit communication protocols in their infrastructure that handle serialized data from authenticated users, particularly those using Java serialization, pickle, YAML parsing, or similar deserialization mechanisms.

RemediationAI

Without vendor advisory links or patch version numbers in the provided data, general remediation guidance is: (1) Apply vendor-supplied security patches immediately when released—monitor vendor security pages for CVE-2025-30023 updates; (2) If patching is delayed, implement network segmentation to restrict client-server communication to authorized network segments only; (3) Enforce strong authentication and monitor for unusual account activity or authentication from unexpected network locations; (4) Disable or restrict the affected communication protocol if possible until patches are deployed; (5) Implement input validation and serialization controls at the application layer if protocol-level fixes are unavailable; (6) Review application logs for suspicious deserialization events or unexpected object instantiation. Vendors should provide specific patch versions and deployment timelines in their security advisories.