dbcve.org
Incontrol WebApplication · Intelbras

CVE-2025-6765

HIGH · 8.8 CVSS v3.1 Published 2025-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability, which was classified as critical, has been found in Intelbras InControl 2.21.60.9. This issue affects some unknown processing of the file /v1/operador/ of the component HTTP PUT Request Handler. The manipulation leads to permission issues. The attack may be initiated 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A critical permission bypass vulnerability exists in Intelbras InControl version 2.21.60.9 within the HTTP PUT request handler for the /v1/operador/ endpoint. The issue allows remote attackers to manipulate operator-level functions due to improper authorization checks, enabling potential privilege escalation or unauthorized administrative access.

MitigationSince Intelbras has not responded to the disclosure, apply compensating controls such as web application firewall rules to block unauthorized PUT requests to /v1/operador/, implement network segmentation to limit exposure, and restrict access to the management interface to trusted IPs only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Incontrol WebApplication
Affected:= 2.21.60.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Intelbras InControl installation
    Locate the InControl web application in your environment. Check running services, installed applications, or web server configurations for Intelbras InControl. Look for process names, service names, or web application directories containing 'incontrol' or 'intelbras'.
    Affected if Intelbras InControl version 2.21.60.9 is installed and running
  2. Confirm installed version
    Access the InControl web interface or check application files for the exact version number. This is typically found in the application's about page, version info endpoint, or in the application binaries/configuration files.
    Affected if The installed version is exactly 2.21.60.9
  3. Verify endpoint exposure
    Check your firewall, reverse proxy, or web server configuration to determine if the /v1/operador/ API endpoint is externally accessible. Review network access control lists and routing rules.
    Affected if The /v1/operador/ endpoint is reachable from untrusted networks
  4. Test PUT request handling
    Send an HTTP PUT request to the /v1/operador/ endpoint using a tool like curl or Burp Suite. Observe whether the request is processed without proper authorization validation.
    Affected if PUT requests to /v1/operador/ are accepted without requiring proper authentication or authorization

You are affected if Intelbras InControl version 2.21.60.9 is running AND the /v1/operador/ endpoint is accessible, allowing unauthorized PUT requests to bypass authorization controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since Intelbras has not responded to the disclosure, apply compensating controls such as web application firewall rules to block unauthorized PUT requests to /v1/operador/, implement network segmentation to limit exposure, and restrict access to the management interface to trusted IPs only.

Recommended fix Low confidence
  1. Isolate the affected InControl Web server from untrusted networks since the vulnerability is remotely exploitable
  2. Implement network-level access controls to limit who can reach the /v1/operador/ endpoint
  3. Monitor vendor channels (Intelbras) for any official security updates or responses
  4. Consider disabling the HTTP PUT functionality for the /v1/operador/ endpoint if not required for business operations
  5. Review user access permissions and ensure least-privilege principles are applied to operator accounts

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Incontrol Web Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6765 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6765 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data