CVE-2025-12063 in AXIS Camera Station Proinfo

Summary

by MITRE • 02/10/2026

An insecure direct object reference allowed a non-admin user to modify or remove certain data objects without having the appropriate permissions.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 02/18/2026

This vulnerability represents a critical access control flaw that fundamentally undermines the security model of the affected system. The issue stems from an insecure direct object reference weakness that allows unauthorized users to manipulate data objects directly through predictable identifiers or references. A non-admin user can exploit this vulnerability to modify or remove specific data objects that should only be accessible to authorized administrators or users with appropriate permissions. The vulnerability directly violates the principle of least privilege and proper access control enforcement that forms the foundation of secure application design.

The technical implementation of this flaw typically occurs when applications use user-supplied input to directly reference objects without performing adequate authorization checks. This pattern creates a pathway where attackers can enumerate or guess object identifiers and subsequently access or modify resources they should not be permitted to interact with. The vulnerability may manifest through predictable URL parameters, database record IDs, file names, or other direct references that are not properly validated against the user's authorization context. This type of weakness is classified as CWE-284 according to the CWE standard, which specifically addresses improper access control mechanisms.

The operational impact of this vulnerability extends far beyond simple data modification or deletion capabilities. An attacker with access to this vulnerability can potentially compromise data integrity, availability, and confidentiality within the affected system. The ability to remove critical data objects can lead to denial of service conditions, while unauthorized modifications can result in data corruption or the introduction of malicious content. This vulnerability particularly affects systems where administrative functions are exposed through direct object references rather than through proper service interfaces or API endpoints. The exploitation of such vulnerabilities often aligns with techniques described in the ATT&CK framework under the privilege escalation and persistence tactics, as attackers can use this access to maintain unauthorized control over system resources.

Mitigation strategies for this vulnerability require implementing robust access control mechanisms that enforce proper authorization checks before allowing any object manipulation operations. The system must validate that the requesting user has appropriate permissions for the specific object being accessed or modified, regardless of how the object reference was obtained. Implementing indirect object references, where internal identifiers are used instead of direct object references, can significantly reduce the attack surface. Additionally, proper input validation, parameterized queries, and comprehensive logging of access attempts can help detect and prevent exploitation attempts. Regular security testing including penetration testing and code reviews should specifically target these access control patterns to identify and remediate similar vulnerabilities before they can be exploited by malicious actors.

Responsible

Axis

Reservation

10/22/2025

Disclosure

02/10/2026

Moderation

accepted

CPE

ready

EPSS

0.00008

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!