Cyber Resilience

CVE-2025-27222

Path Traversal in Rocketsoftware Trufusion Enterprise ≤ 7.10.4.0

Public PoCPath Traversal
Published
27 October 2025
Modified
03 November 2025
Patch / advisory
CVSS Score v3.1 8.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS Score 0.019 77th percentile
Risk Priority 69 floored blend · peak EPSS

Summary

CVE-2025-27222 is a high-severity Path Traversal (CWE-22) vulnerability in Rocketsoftware Trufusion Enterprise. Its CVSS base score is 8.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 23% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-27222 is a path traversal vulnerability (CWE-22, CWE-35) in TRUfusion Enterprise through version 7.10.4.0. The affected component is the /trufusionPortal/getCobrandingData endpoint, which retrieves files but fails to properly sanitize input. This allows inclusion of path traversal sequences, enabling retrieval of any local server file accessible by the TRUfusion user, including cleartext passwords stored by TRUfusion Enterprise itself. The vulnerability carries a CVSS v3.1 base score of 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N).

Unauthenticated attackers with network access can exploit this vulnerability with low attack complexity and no user interaction. Exploitation involves sending crafted requests to the endpoint, achieving high-impact confidentiality violations in a scoped manner by reading arbitrary accessible files. This includes sensitive data like TRUfusion Enterprise passwords, potentially enabling further compromise such as lateral movement or privilege escalation depending on file contents and server permissions.

Advisories provide further details on the issue, including a GitHub advisory at https://github.com/MrTuxracer/advisories/blob/master/CVEs/CVE-2025-27222.txt and an RCE Security post at https://www.rcesecurity.com/2025/09/when-audits-fail-four-critical-pre-auth-vulnerabilities-in-trufusion-enterprise/ covering this and three other pre-auth vulnerabilities in TRUfusion Enterprise. The vendor product page is at https://www.rocketsoftware.com/products/rocket-b2b-supply-chain-integration/rocket-trufusion-enterprise. Security practitioners should review these for patch availability and mitigation steps.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

TRUfusion Enterprise through 7.10.4.0 uses the /trufusionPortal/getCobrandingData endpoint to retrieve files. However, the application doesn't properly sanitize the input to this endpoint, ultimately allowing path traversal sequences to be included. This can be used to read any local server file…

more

that is accessible by the TRUfusion user and can also be used to leak cleartext passwords of TRUfusion Enterprise itself.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-0067Shared CWE-22, CWE-35
CVE-2024-2654Shared CWE-22, CWE-35
CVE-2025-41736Shared CWE-22, CWE-35
CVE-2023-21418Shared CWE-22, CWE-35
CVE-2025-40573Shared CWE-22, CWE-35
CVE-2024-49770Shared CWE-22, CWE-35
CVE-2023-5885Shared CWE-22, CWE-35
CVE-2025-26935Shared CWE-22, CWE-35
CVE-2024-52885Shared CWE-22, CWE-35
CVE-2024-1886Shared CWE-22, CWE-35

Affected Assets

rocketsoftware
trufusion enterprise
≤ 7.10.4.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Input validation directly neutralizes special path elements before pathname construction occurs.

Enforces information flow rules that stop unauthorized directory escapes via crafted paths.

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that neutralize traversal sequences.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

mitigates

Information access restriction limits which files an application may read or write.

References