Skip to main content
VulnerabilityPublished Updated

CVE-2025-54769: Xorux LPAR2RRD · Path Traversal: '../filedir

Affects Xorux LPAR2RRDSource CVE Database V5

0

Public exploit available (Exploit-DB) · CVSS 8.8 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.3% chance of exploitation in 30 days – higher than 88% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 28 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by KoreLogic Security

    , 8 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 13 minutes after disclosure

  4. First Exploit-DB entry (opens in a new tab)

    LPAR2RRD 8.04 - Remote Code Execution (RCE)

    , 6 days after disclosure

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 24 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Xorux LPAR2RRDAffected
  • =8.04
Fixed in–

AI-suggested

Given the absence of an official patch, European organizations should implement immediate compensating controls. These include restricting file upload capabilities strictly to trusted users and limiting the directories where files can be uploaded through filesystem permissions and application configuration. Employ application-layer filtering to sanitize and validate file paths rigorously, preventing directory traversal sequences. Monitor file system integrity for unexpected changes to PERL modules or other critical application files using file integrity monitoring tools. Isolate LPAR2RRD instances within segmented network zones to limit lateral movement if compromised. Employ strict authentication and access controls, including multi-factor authentication for all users with upload privileges. Regularly audit logs for suspicious upload activities and anomalous application behavior. Engage with Xorux for updates and patches, and plan for rapid deployment once available. Consider deploying web application firewalls (WAFs) with custom rules to detect and block directory traversal attempts.

Description

An authenticated, read-only user can upload a file and perform a directory traversal to have the uploaded file placed in a location of their choosing. This can be used to overwrite existing PERL modules within the application to achieve remote code execution (RCE) by an attacker.

References

Community reviews

Loading reviews…