# CVE-2024-5539: ALC WebCTRL Carrier i-Vu Access Control Bypass

> Attackers can bypass access restrictions on ALC WebCTRL and Carrier i-Vu building automation servers to expose sensitive information.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Nov 2025
- **Updated:** 28 Nov 2025
- **Also known as:** GHSA-2m76-j3f4-m2c2

## What is CVE-2024-5539?

CVE-2024-5539 is a critical authentication bypass vulnerability in Automated Logic WebCTRL, published on 27 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Access Control Bypass vulnerability found in ALC WebCTRL and Carrier i-Vu in versions up to and including 8.5 allows a malicious actor to bypass intended access restrictions and expose sensitive information via the 

web based building automation server.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-5539?


## How do I fix CVE-2024-5539?

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

## Is CVE-2024-5539 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5539 and fix it if it is affected.

What it is: CVE-2024-5539 is a critical authentication bypass vulnerability in Automated Logic WebCTRL, published on 27 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5539 in the wild and no public exploit code.

Affected product: Automated Logic WebCTRL. 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-2024-5539/ (Markdown: https://insights.sbomify.com/CVE-2024-5539/index.md)
```

## Sources

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

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