dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-41028

CRITICAL · 9.3 CVSS v4.0 Published 2025-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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’.

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 confidence

SQL Injection vulnerability in Epsilon RH by Grupo Castilla allows unauthenticated attackers to manipulate the database via the 'sEstadoUsr' parameter in the /epsilonnetws/WSAvisos.asmx web service endpoint. The lack of proper input sanitization or parameterized queries enables full database compromise including retrieval, creation, update, and deletion of data.

MitigationImplement parameterized queries or prepared statements for all SQL operations in the WSAvisos.asmx web service, specifically validating and sanitizing the 'sEstadoUsr' parameter before database execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Epsilon RH installation
    Locate the web application directory or identify the hosted site named 'epsilonnetws' or 'Epsilon RH' in your web server (IIS, Apache, etc.) configuration
    Affected if The Epsilon RH web application by Grupo Castilla is present in the environment
  2. Verify WSAvisos.asmx endpoint exists
    Access the URL path /epsilonnetws/WSAvisos.asmx via HTTP/HTTPS request and confirm the ASMX service page loads or returns a SOAP response
    Affected if The WSAvisos.asmx web service endpoint is accessible and responds to requests
  3. Identify sEstadoUsr parameter handling
    Review the application source code or decompiled binaries for the WSAvisos.asmx service, specifically looking for the method handling the sEstadoUsr POST parameter
    Affected if The code accepts the sEstadoUsr parameter without parameterized query implementation
  4. Confirm lack of input validation
    Inspect the code handling sEstadoUsr to verify whether SQL meta-characters are validated or sanitized before being used in database queries
    Affected if No input validation or sanitization for SQL meta-characters is present in the parameter handling code

The environment is affected if Epsilon RH is installed with the WSAvisos.asmx endpoint accessible and the sEstadoUsr parameter is processed without parameterized queries or input validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for all SQL operations in the WSAvisos.asmx web service, specifically validating and sanitizing the 'sEstadoUsr' parameter before database execution.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41028 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41028 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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