CVE-2025-11851VulnerabilityPublished 16 Oct 2025

CVE-2025-11851: Apeman ID71 · Cross Site Scripting

Affects Apeman ID71Source CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Oct 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

Affected software

Product	Affected	Fixed in
Apeman ID71	Affected =75.8.53.20	Fixed in–

AI-suggested

1. Restrict network access to the /set_alias.cgi endpoint by implementing firewall rules or network segmentation to limit exposure only to trusted management networks. 2. Deploy web application firewalls (WAFs) with robust XSS detection and blocking capabilities to intercept malicious payloads targeting the alias parameter. 3. Educate users and administrators about the risks of clicking on unsolicited or suspicious links that could trigger XSS attacks. 4. Monitor device logs and network traffic for unusual requests or patterns indicative of exploitation attempts. 5. If possible, disable or restrict the functionality of the vulnerable endpoint until a vendor patch is available. 6. Consider deploying reverse proxies or security gateways that can sanitize input parameters before forwarding requests to the device. 7. Maintain an inventory of all Apeman ID71 devices and prioritize patching or replacement plans once vendor updates are released. 8. Engage with Apeman support channels persistently to seek official remediation or guidance. 9. Implement multi-factor authentication and strong session management on management interfaces to reduce the impact of session hijacking. 10. Regularly review and update incident response plans to include scenarios involving XSS exploitation on security devices.

Description

A vulnerability has been found in Apeman ID71 EN75.8.53.20. The affected element is an unknown function of the file /set_alias.cgi. Such manipulation of the argument alias leads to cross site scripting. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the impact of CVE-2025-11851 could be significant in sectors relying on Apeman ID71 devices, such as physical security, surveillance, or access management. Successful exploitation could lead to unauthorized access to user sessions, enabling attackers to perform actions on behalf of legitimate users or steal sensitive information. This could compromise the integrity of security systems, potentially allowing attackers to bypass controls or manipulate device configurations. Additionally, XSS attacks can serve as a vector for delivering further malware or phishing campaigns targeting employees or administrators. The lack of vendor patches means organizations must rely on network-level protections and user awareness to mitigate risk. Disruption or compromise of security devices could have cascading effects on operational continuity and regulatory compliance, especially under GDPR and other European data protection frameworks. The medium severity rating suggests a moderate but tangible risk that should not be ignored, particularly in critical infrastructure or high-value environments.

Summary

CVE-2025-11851 identifies a cross-site scripting (XSS) vulnerability in the Apeman ID71 device firmware version EN75.8.53.20. The vulnerability resides in an unspecified function within the /set_alias.cgi endpoint, where the alias parameter is not properly sanitized or encoded, allowing an attacker to inject malicious JavaScript code. This flaw can be exploited remotely without requiring authentication, although user interaction is necessary, typically by tricking a user into visiting a crafted URL containing the malicious payload. The vulnerability impacts the confidentiality and integrity of user sessions by enabling script execution in the victim’s browser context, which can lead to session hijacking, credential theft, or redirection to malicious sites. The vendor was notified early but has not issued a patch or mitigation guidance, and no public exploits have been confirmed in the wild yet. The CVSS 4.0 score of 5.1 reflects a medium severity, considering the ease of remote exploitation, lack of authentication, but requirement for user interaction and limited impact on system availability. This vulnerability is particularly concerning for environments where the Apeman ID71 is used in security-sensitive roles, such as surveillance or access control, as attackers could leverage XSS to escalate attacks or disrupt operations. The absence of vendor response increases the urgency for organizations to implement compensating controls and monitor for exploitation attempts.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Oct 2025, 16:29 UTC

Technical details

References

Community reviews

Related threats