# CVE-2024-40407: Information disclosure in n/a

> Attackers can obtain the application's root path, potentially aiding further attacks, affecting Thinfinity Workspace users.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2024
- **Updated:** 25 Nov 2024
- **Also known as:** GHSA-5phw-w7h3-vg96

## What is CVE-2024-40407?

CVE-2024-40407 is a high-severity vulnerability in n/a, published on 13 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A full path disclosure in Cybele Software Thinfinity Workspace before v7.0.2.113 allows attackers to obtain the root path of the application via unspecified vectors.

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

It affects 1 product.


Products: Cybelesoft Thinfinity Workspace.

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

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

## Is CVE-2024-40407 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-40404](https://insights.sbomify.com/CVE-2024-40404/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-40405](https://insights.sbomify.com/CVE-2024-40405/): Missing authorization in n/a (high 8.1)
- [CVE-2024-40408](https://insights.sbomify.com/CVE-2024-40408/): Missing authorization in n/a (high 7.3)
- [CVE-2024-40410](https://insights.sbomify.com/CVE-2024-40410/): Hardcoded credentials in n/a (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-40407 is a high-severity vulnerability in n/a, published on 13 Nov 2024. 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-2024-40407 in the wild and no public exploit code.

Affected product: n/a. 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-40407/ (Markdown: https://insights.sbomify.com/CVE-2024-40407/index.md)
```

## Sources

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

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