# CVE-2019-25618: AdminExpress 1.2.5 Denial of Service via System Compare

> Local attackers can crash AdminExpress by submitting oversized input to the System Compare feature, causing application unresponsiveness.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **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 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-r9wh-j382-4f93

## What is CVE-2019-25618?

CVE-2019-25618 is a medium-severity denial of service vulnerability in Admin-Express AdminExpress, published on 22 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AdminExpress 1.2.5 contains a denial of service vulnerability that allows local attackers to crash the application by submitting oversized input through the System Compare feature. Attackers can paste a large buffer of characters into the Folder Path field and trigger the comparison function to cause the application to become unresponsive or crash.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2019-25618?


## How do I fix CVE-2019-25618?

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

## Is CVE-2019-25618 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25618 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25618 and fix it if it is affected.

What it is: CVE-2019-25618 is a medium-severity denial of service vulnerability in Admin-Express AdminExpress, published on 22 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25618 exists.

Affected product: Admin-Express AdminExpress. 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-2019-25618/ (Markdown: https://insights.sbomify.com/CVE-2019-25618/index.md)
```

## Sources

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

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