CVE-2025-8515VulnerabilityPublished 4 Aug 2025Updated 29 Oct 2025

CVE-2025-8515: Intelbras InControl · Information Disclosure

Affects Intelbras InControlSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

2.3Low

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

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

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

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
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: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
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: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system 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 Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within 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 4 Aug 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
Intelbras InControl	Affected =2.21.60.9	Fixed in–

AI-suggested

1. Apply vendor-provided updates or patches for Intelbras InControl as soon as they become available to address CVE-2025-8515. 2. Restrict network access to the /v1/operador/ JSON endpoint by implementing firewall rules or network segmentation to limit exposure to trusted administrators only. 3. Enforce strict access controls and monitor logs for unusual or unauthorized access attempts to the management interface. 4. Use network intrusion detection systems (NIDS) to detect anomalous JSON requests targeting the vulnerable endpoint. 5. Conduct regular security assessments and penetration testing focused on Intelbras InControl deployments to identify any exploitation attempts. 6. Educate system administrators about the vulnerability and encourage prompt reporting of suspicious activity. 7. If possible, disable or limit the functionality of the affected endpoint until a patch is applied. These steps go beyond generic advice by focusing on network-level restrictions, monitoring, and operational controls tailored to the specific vulnerable component.

Description

A weakness has been identified in Intelbras InControl 2.21.60.9. This vulnerability affects unknown code of the file /v1/operador/ of the component JSON Endpoint. Executing manipulation can lead to information disclosure. It is possible to launch the attack remotely. A high complexity level is associated with this attack. It is stated that the exploitability is difficult. The exploit has been made available to the public and could be exploited. Upgrading the affected component is advised.

Impact

For European organizations, the primary impact of CVE-2025-8515 is unauthorized disclosure of potentially sensitive information managed by Intelbras InControl systems. This could lead to exposure of operational details or user data, which may facilitate further targeted attacks or privacy violations. However, the low severity and high complexity reduce the likelihood of widespread exploitation. Organizations relying on Intelbras InControl for network or security management should be aware that attackers with network access and some privileges could leverage this flaw to gain intelligence about the system. This could be particularly concerning for critical infrastructure or enterprises with sensitive operational environments. The lack of impact on integrity or availability means system operations are unlikely to be disrupted directly by this vulnerability. Nonetheless, information disclosure can have cascading effects on security posture and compliance with data protection regulations such as GDPR.

Summary

CVE-2025-8515 identifies a security weakness in Intelbras InControl version 2.21.60.9, specifically within the JSON endpoint located at /v1/operador/. This endpoint processes JSON requests related to operator functions. The vulnerability allows an attacker to remotely manipulate requests to this endpoint to disclose sensitive information. The exact nature of the leaked information is unspecified but typically could include configuration data, user details, or operational parameters. Exploitation does not require user interaction and can be performed remotely over the network, but it requires low privileges and is rated as having high complexity, indicating that successful exploitation demands significant technical skill or specific conditions. The CVSS 4.0 vector (AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P) reflects a network attack vector with high attack complexity, no user interaction, and low impact on confidentiality only. No integrity or availability impacts are noted. Although an exploit has been publicly disclosed, no widespread exploitation has been observed in the wild. Intelbras has advised upgrading the affected component to remediate the vulnerability, but no direct patch links are provided in the source. The vulnerability is classified as low severity due to limited impact and difficult exploitability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2025, 07:31 UTC

Technical details

References

Community reviews

Related threats