# CVE-2025-53187: Unauthenticated RCE

> Unauthenticated attackers can bypass authentication to execute code, access files, and modify system time in ABB ASPECT due to debug code in production.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 11 Aug 2025
- **Updated:** 4 Sep 2025
- **Also known as:** GHSA-xqxh-xcx3-fff7

## What is CVE-2025-53187?

CVE-2025-53187 is a critical authentication bypass vulnerability in ABB ASPECT, published on 11 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Due to an issue in configuration, code that was intended for debugging purposes was included in the market release of the ASPECT FW allowing an attacker to bypass authentication. This vulnerability may allow an attacker to change the system time, access files, and make function calls without prior authentication. This issue affects all versions of ASPECT prior to 3.08.04-s01

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2025-53187 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53187 is a critical authentication bypass vulnerability in ABB ASPECT, published on 11 Aug 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-2025-53187 in the wild and no public exploit code.

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

## Sources

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

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