# CVE-2025-41028: SQL injection in Epsilon RH

> An attacker can manipulate the database via SQL injection in the Epsilon RH web service, allowing data retrieval and modification.

- **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:** 20 Oct 2025
- **Updated:** 20 Oct 2025
- **Also known as:** GHSA-9c6x-55mp-cvpv

## What is CVE-2025-41028?

CVE-2025-41028 is a critical SQL injection vulnerability in Grupo Castilla Epsilon RH, published on 20 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A SQL Injection vulnerability has been found in Epsilon RH by Grupo Castilla. This vulnerability allows an attacker to retrieve, create, update and delete database via sending a POST request using the parameter ‘sEstadoUsr’ in ‘/epsilonnetws/WSAvisos.asmx’.

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

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


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

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

## Is CVE-2025-41028 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41028 is a critical SQL injection vulnerability in Grupo Castilla Epsilon RH, published on 20 Oct 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-41028 in the wild and no public exploit code.

Affected product: Grupo Castilla Epsilon RH. 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-41028/ (Markdown: https://insights.sbomify.com/CVE-2025-41028/index.md)
```

## Sources

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

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