# CVE-2025-12461: Unprotected access to parts of the application in Epsilon RH by Grupo Castilla

> Attackers can access unprotected application paths to obtain sensitive license and configuration information without authentication.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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:** 29 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-vch3-8jh3-g32c

## What is CVE-2025-12461?

CVE-2025-12461 is a medium-severity missing authorization vulnerability in Grupo Castilla Epsilon RH, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This vulnerability allows an attacker to access parts of the application that are not protected by any type of access control.  The attacker could access this path ‘…/epsilonnet/License/About.aspx’ and obtain information on both the licence and the configuration of the product by knowing which modules are installed.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2025-12461 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12461 is a medium-severity missing authorization vulnerability in Grupo Castilla Epsilon RH, published on 29 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-12461 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-12461/ (Markdown: https://insights.sbomify.com/CVE-2025-12461/index.md)
```

## Sources

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

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