# CVE-2025-22953: SQL injection in n/a

> Attackers can inject SQL into the JsonFetcher.svc filter parameter to read data or execute code if xp_cmdshell is enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2025
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-q87j-52xg-48j5

## What is CVE-2025-22953?

CVE-2025-22953 is a critical SQL injection vulnerability in n/a, published on 28 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A SQL injection vulnerability exists in Epicor HCM 2021 1.9, with patches available: 5.16.0.1033/HCM2022, 5.17.0.1146/HCM2023, and 5.18.0.573/HCM2024. The injection is specifically in the filter parameter of the JsonFetcher.svc endpoint. An attacker can exploit this vulnerability by injecting malicious SQL payloads into the filter parameter, enabling the unauthorized execution of arbitrary SQL commands on the backend database. If certain features (like xp_cmdshell) are enabled, this may lead to remote code execution.

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

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

It affects 1 product.


Products: Epicor Human Capital Management.

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

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

## Is CVE-2025-22953 being exploited?

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

Public exploit code:

- EPICOR HCM Unauthenticated Blind SQL Injection CVE-2025-22953 (github_poc): https://github.com/maliktawfiq/CVE-2025-22953

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22953 is a critical SQL injection vulnerability in n/a, published on 28 Mar 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-22953 in the wild and no public exploit code.

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

## Sources

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

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