VulnerabilityPublished 13 Nov 2024Updated 25 Nov 2024

CVE-2024-40407: A Full Path Disclosure

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in 7.0.2.113 : patch Cybele Software Thinfinity Workspace soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects: Cybele Software Thinfinity Workspace before 7.0.2.113
Patch: Available – fixed in 7.0.2.113

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-40407, organizations should immediately upgrade Thinfinity Workspace to version 7.0.2.113 or later, where the vulnerability is addressed. In the absence of an immediate upgrade path, network-level mitigations should be implemented, including restricting access to Thinfinity Workspace interfaces to trusted IP addresses and deploying web application firewalls (WAFs) configured to detect and block suspicious requests that may attempt to trigger path disclosure. Additionally, administrators should audit server configurations to ensure error messages and debug information do not leak file system paths. Monitoring network traffic and application logs for unusual or repeated requests that could indicate reconnaissance attempts is also recommended. Employing network segmentation to isolate Thinfinity Workspace servers from less trusted networks can reduce exposure. Finally, organizations should maintain an up-to-date inventory of affected assets and apply security patches promptly upon release.

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.

Impact

The primary impact of CVE-2024-40407 is the disclosure of sensitive information about the internal file system structure of Thinfinity Workspace deployments. This information leakage compromises confidentiality and can significantly aid attackers in crafting more effective attacks, such as identifying configuration files, sensitive scripts, or other exploitable resources. Although the vulnerability does not directly compromise data integrity or system availability, the knowledge gained from the disclosed paths can be a stepping stone for more severe attacks, including privilege escalation or remote code execution if combined with other vulnerabilities. Organizations using Thinfinity Workspace in environments with sensitive data or critical operations face increased risk of targeted attacks. The vulnerability’s ease of exploitation and lack of authentication requirements mean that attackers can scan and exploit vulnerable systems at scale, potentially leading to widespread reconnaissance and subsequent attacks. The absence of known exploits in the wild currently limits immediate risk but does not reduce the urgency for mitigation.

References

blog.cybelesoft.com/thinfinity-workspace-security-bulletin-nov-2024/ (opens in a new tab)

Community reviews

Loading reviews…