# CVE-2024-10651: CHANGING Information Technology IDExpert - Arbitrary File Read through Path Traversal

> Administrators can exploit a path traversal flaw in IDExpert to read arbitrary system files, exposing sensitive data.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2024
- **Updated:** 1 Nov 2024
- **Also known as:** GHSA-q489-4f3v-w8rm

## What is CVE-2024-10651?

CVE-2024-10651 is a medium-severity path traversal vulnerability in CHANGING Information Technology IDExpert, published on 1 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IDExpert from CHANGING Information Technology does not properly validate a specific parameter in the administrator interface, allowing remote attackers with administrator privileges to exploit this vulnerability to read arbitrary system files.

Weakness: CWE-36 (Absolute Path Traversal)

## Which versions are affected by CVE-2024-10651?


## How do I fix CVE-2024-10651?

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

## Is CVE-2024-10651 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10651 and fix it if it is affected.

What it is: CVE-2024-10651 is a medium-severity path traversal vulnerability in CHANGING Information Technology IDExpert, published on 1 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10651 in the wild and no public exploit code.

Affected product: CHANGING Information Technology IDExpert. 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-2024-10651/ (Markdown: https://insights.sbomify.com/CVE-2024-10651/index.md)
```

## Sources

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

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