CVE-2025-31512VulnerabilityPublished 22 Jul 2025Updated 18 Aug 2025

CVE-2025-31512: n/a

Source CVE Database V5

Not known to be exploited · CVSS 7.3 High · fixed in 4.1.14.1.5.32 : patch affected systems soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.3High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.1.14.1.5.32, 4.1.14.0.48, 4.1.14.0.43 +8

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

European organizations should prioritize upgrading AlertEnterprise Guardian to one of the vendor-recommended build versions or later to remediate this vulnerability. Beyond patching, organizations should implement compensating controls such as enhanced monitoring and logging of access requests and approvals to detect anomalous activities. Multi-factor authentication (MFA) for access request submissions and managerial approvals can add an additional security layer. Regular audits of access control policies and periodic penetration testing focusing on physical access management systems are advisable. Network segmentation should be enforced to isolate access control systems from general IT networks, reducing the attack surface. Additionally, organizations should train security and facilities management personnel to recognize and respond to suspicious access requests promptly. Incident response plans should be updated to include scenarios involving physical access control bypasses.

Description

An issue was discovered in AlertEnterprise Guardian 4.1.14.2.2.1. One can bypass manager approval via isAddedByApprover in a Request%20Building%20Access requestSubmit API call. The vendor has stated that the system is protected by updating to a version equal to or greater than one of the following build numbers: 4.1.12.2.1.19, 4.1.12.5.2.36, 4.1.13.0.60, 4.1.13.2.0.3.39, 4.1.13.2.0.3.41, 4.1.13.2.42, 4.1.13.2.25.44, 4.1.14.0.13, 4.1.14.0.43, 4.1.14.0.48, and 4.1.14.1.5.32.

Impact

For European organizations, this vulnerability poses a substantial risk, especially for enterprises relying on AlertEnterprise Guardian for physical access management. Unauthorized bypass of manager approval can lead to unauthorized physical access to sensitive facilities, potentially resulting in theft, espionage, or sabotage. The breach of physical security controls can also facilitate further cyber intrusions if attackers gain access to internal networks or systems. Confidentiality may be compromised if sensitive information is accessed or exfiltrated, integrity could be affected if unauthorized changes are made to access logs or configurations, and availability might be impacted if access control systems are manipulated to deny legitimate users. Given the critical nature of physical security in sectors like finance, government, healthcare, and critical infrastructure across Europe, the threat could have cascading effects on operational continuity and regulatory compliance, including GDPR implications if personal data is involved.

Summary

CVE-2025-31512 is a security vulnerability identified in AlertEnterprise Guardian version 4.1.14.2.2.1. The flaw allows an attacker to bypass the manager approval process in the system's Request Building Access functionality by manipulating the 'isAddedByApprover' parameter in the requestSubmit API call. This bypass effectively undermines the intended access control mechanism, enabling unauthorized users to gain building access without proper managerial consent. The vulnerability is classified under CWE-288, which relates to improper authentication. The CVSS v3.1 base score is 7.3, indicating a high severity level, with attack vector being network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), and no user interaction needed (UI:N). The impact affects confidentiality, integrity, and availability, albeit at a low level for each, as unauthorized access could lead to potential information exposure, unauthorized modifications, or disruption of access control processes. The vendor has addressed this issue in multiple subsequent builds starting from versions 4.1.12.2.1.19 and later, recommending upgrades to these or newer versions to mitigate the risk. No known exploits are currently reported in the wild, but the ease of exploitation and lack of required privileges make this a significant threat if left unpatched.

CWE-288Authentication Bypass Using an Alternate Path or Channel (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product requires authentication, but the product has an alternate path or channel that does not require authentication.
Architecture and Design
Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
V1.2.4 (opens in a new tab)
Attack patterns
Directory Indexing (opens in a new tab)
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 19 Aug 2025, 01:13 UTC

WeaknessesCWE-288

Technical details

References

Community reviews

Related threats