# CVE-2025-2585: EBM Technologies EBM Maintenance Center - SQL injection

> Remote attackers with regular privileges can inject SQL commands to read, modify, and delete database contents in EBM Maintenance Center.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2025
- **Updated:** 21 Mar 2025
- **Also known as:** GHSA-7m7p-4552-89x5

## What is CVE-2025-2585?

CVE-2025-2585 is a high-severity SQL injection vulnerability in EBM Maintenance Center, published on 21 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

EBM Maintenance Center From EBM Technologies has a SQL Injection vulnerability, allowing remote attackers with regular privileges to inject arbitrary SQL commands to read, modify, and delete database contents.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2025-2585 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2585 is a high-severity SQL injection vulnerability in EBM Maintenance Center, published on 21 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2585 in the wild and no public exploit code.

Affected product: EBM Maintenance Center. 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-2585/ (Markdown: https://insights.sbomify.com/CVE-2025-2585/index.md)
```

## Sources

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

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