# CVE-2025-41020: Insecure direct object reference (IDOR) vulnerability in Sergestec's Exito

> Attackers can access other customers' data by manipulating the ID parameter in the admin ticket interface of Sergestec Exito.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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:** 16 Oct 2025
- **Updated:** 16 Oct 2025
- **Also known as:** GHSA-m8pw-9fx4-mvpr

## What is CVE-2025-41020?

CVE-2025-41020 is a high-severity missing authorization vulnerability in Sergestec Exito, published on 16 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insecure direct object reference (IDOR) vulnerability in Sergestec's Exito v8.0. This vulnerability allows an attacker to access data belonging to other customers through the 'id' parameter in '/admin/ticket_a4.php'.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Sergestec Exito.

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

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

## Is CVE-2025-41020 being exploited?

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

## Other vulnerabilities in Sergestec Exito

- [CVE-2025-41018](https://insights.sbomify.com/CVE-2025-41018/): SQL injection vulnerability in Sergestec's Exito (critical 9.3)
- [CVE-2025-41021](https://insights.sbomify.com/CVE-2025-41021/): Stored Cross-Site Scripting (XSS) vulnerability in Sergestec's Exito (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41020 is a high-severity missing authorization vulnerability in Sergestec Exito, published on 16 Oct 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-41020 in the wild and no public exploit code.

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

## Sources

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

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