# CVE-2024-48851: Remote Code Execution

> Remote attackers can execute arbitrary code on ABB FLXEON systems due to improper input validation, posing a critical risk to industrial operations.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2025
- **Updated:** 18 Sep 2025
- **Also known as:** GHSA-chxc-9v7p-7xgg

## What is CVE-2024-48851?

CVE-2024-48851 is a high-severity code injection vulnerability in ABB FLXEON, published on 18 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Validation of Specified Type of Input vulnerability in ABB FLXEON.A remote code execution is possible due to an improper input validation.

This issue affects FLXEON: through 9.3.5.

Weakness: CWE-1287 (Improper Validation of Specified Type of Input)

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


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

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

## Is CVE-2024-48851 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48851 is a high-severity code injection vulnerability in ABB FLXEON, published on 18 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-48851 in the wild and no public exploit code.

Affected product: ABB FLXEON. 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-48851/ (Markdown: https://insights.sbomify.com/CVE-2024-48851/index.md)
```

## Sources

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

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