# CVE-2026-6284: Horner Automation Cscape and XL4, XL7 PLC Weak password requirements

> Attackers can brute force weak PLC passwords due to lack of complexity requirements and input limits, gaining unauthorized access.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/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:** 17 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-r9f4-h79v-5p47

## What is CVE-2026-6284?

CVE-2026-6284 is a critical vulnerability in Horner Automation Cscape, published on 17 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An attacker with network access to the PLC is able to brute force discover passwords to gain unauthorized access to systems and services. The limited password complexity and no password input limiters makes brute force password enumeration possible.

Weakness: CWE-521 (Weak Password Requirements)

## Which versions are affected by CVE-2026-6284?


## How do I fix CVE-2026-6284?

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

## Is CVE-2026-6284 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6284 and fix it if it is affected.

What it is: CVE-2026-6284 is a critical vulnerability in Horner Automation Cscape, published on 17 Apr 2026. 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-2026-6284 in the wild and no public exploit code.

Affected product: Horner Automation Cscape. 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-2026-6284/ (Markdown: https://insights.sbomify.com/CVE-2026-6284/index.md)
```

## Sources

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

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