CVE-2025-22953
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA critical SQL injection vulnerability exists in Epicor HCM 2021 1.9 in the filter parameter of the JsonFetcher.svc endpoint. Attackers can inject malicious SQL payloads to execute arbitrary commands on the backend database, potentially escalating to remote code execution if features like xp_cmdshell are enabled.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2021_1.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Epicor HCM versionLocate the installed Epicor Human Capital Management version through the application admin panel, system information page, or product about dialog. Alternatively, check the registry or installation directory for version metadata if direct access to the application is unavailable.Affected if The installed version is exactly 2021_1.9 (this specific version is affected; other versions may have different patch status).
-
Verify JsonFetcher.svc endpoint existsCheck if the JsonFetcher.svc web service file exists in the deployed application web directory, typically under the HCM web application's accessible paths. This can be confirmed by attempting to access the endpoint URL (for example, https://yourserver/Path/To/JsonFetcher.svc) and checking for a valid SOAP or WSDL response.Affected if The JsonFetcher.svc endpoint is present and responds to HTTP requests, indicating the vulnerable component is exposed.
-
Confirm application is network-accessibleDetermine whether the Epicor HCM web application is accessible from network locations beyond the internal localhost. This includes checking firewall rules, IIS bindings, and reverse proxy configurations that govern external or non-VPN access to the HCM portal.Affected if The HCM application is reachable from network segments that include untrusted users, increasing the likelihood of remote exploitation.
You are affected if your Epicor HCM installation is exactly version 2021_1.9 AND the JsonFetcher.svc endpoint is exposed to potential attackers over the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the available patches: 5.16.0.1033 for HCM2022, 5.17.0.1146 for HCM2023, or 5.18.0.573 for HCM2024. Additionally, disable or restrict xp_cmdshell and other dangerous database features as a defense-in-depth measure.
HCM2024 version 5.18.0.573 (or HCM2023 5.17.0.1146 / HCM2022 5.16.0.1033 depending on support tier)
- 1. Identify your target HCM version (HCM2022, HCM2023, or HCM2024) based on your support agreement and upgrade timeline
- 2. Obtain the corresponding patch from Epicor customer portal or contact Epicor support: HCM2022 requires 5.16.0.1033, HCM2023 requires 5.17.0.1146, HCM2024 requires 5.18.0.573
- 3. Review the patch release notes for any prerequisites, known issues, or configuration changes required
- 4. Create a full backup of the database and application files before applying the patch
- 5. Test the patch in a non-production environment to verify the SQL injection is remediated and no regressions occur
- 6. Apply the patch during a scheduled maintenance window following Epicor's standard deployment procedures
- 7. After patching, validate that the JsonFetcher.svc endpoint filter parameter properly sanitizes input and no longer accepts SQL injection payloads
- 8. If xp_cmdshell was previously enabled as a mitigation, evaluate whether it can be safely disabled post-patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22953 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22953 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data