# CVE-2025-1645: Benner Connecta EditarLogado resource injection

> Remote attackers can exploit improper resource identifier control in Benner Connecta to potentially execute code or escalate privileges.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2025
- **Updated:** 25 Feb 2025
- **Also known as:** GHSA-x5p5-cx32-rppv

## What is CVE-2025-1645?

CVE-2025-1645 is a medium-severity vulnerability in Benner Connecta, published on 25 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in Benner Connecta 1.0.5330. Affected by this vulnerability is an unknown functionality of the file /Usuarios/Usuario/EditarLogado/. The manipulation of the argument Handle leads to improper control of resource identifiers. The attack can be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-99 (Improper Control of Resource Identifiers)

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


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

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

## Is CVE-2025-1645 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1645 is a medium-severity vulnerability in Benner Connecta, published on 25 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1645 in the wild and no public exploit code.

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

## Sources

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

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