# CVE-2025-7705: Authentication bypass due to compatibility mode enabled by default

> Attackers can bypass authentication on ABB Switch Actuators because compatibility mode is enabled by default, allowing unauthorized access.

- **Severity:** High 8.6 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2025
- **Updated:** 22 Jul 2025
- **Also known as:** GHSA-7cwr-3892-8m78

## What is CVE-2025-7705?

CVE-2025-7705 is a high-severity authentication bypass vulnerability in ABB Switch Actuator 4 DU-83330, published on 22 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

: Active Debug Code vulnerability in ABB Switch Actuator 4 DU-83330, ABB Switch actuator, door/light 4 DU -83330-500.This issue affects Switch Actuator 4 DU-83330: All Versions; Switch actuator, door/light 4 DU -83330-500: All Versions.

Weakness: CWE-489 (Active Debug Code)

## Which versions are affected by CVE-2025-7705?


## How do I fix CVE-2025-7705?

No fix has been published for CVE-2025-7705 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-7705 being exploited?

There is no known exploitation of CVE-2025-7705 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7705 and fix it if it is affected.

What it is: CVE-2025-7705 is a high-severity authentication bypass vulnerability in ABB Switch Actuator 4 DU-83330, published on 22 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7705 in the wild and no public exploit code.

Affected product: ABB Switch Actuator 4 DU-83330. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-7705/ (Markdown: https://insights.sbomify.com/CVE-2025-7705/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7705
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7705
- OSV: https://osv.dev/vulnerability/CVE-2025-7705

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-7705/
Summaries are generated and may contain mistakes; the official description above is the record.