CVE-2025-54769 is an authenticated file upload vulnerability combined with directory traversal. According to the provided description, a user with read-only privileges can upload a file and manipulate the upload path so the file is written to an attacker-chosen location. This arbitrary file placement can be used to overwrite existing Perl modules within the application. Because those modules are subsequently loaded or executed by the application, the attacker can leverage the overwrite to achieve remote code execution. The issue therefore appears to stem from insufficient restriction of upload destinations and improper neutralization of path traversal sequences in file paths.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a proof-of-concept exploit for CVE-2025-54769, targeting the LPAR2RRD software. The exploit is implemented in C (exploit.c) and automates the process of achieving remote code execution via a vulnerable CGI endpoint. The workflow is as follows: (1) a malicious Perl CGI script (users.pl) is generated, which executes arbitrary shell commands; (2) the script is uploaded to the target using a POST request to the /lpar2rrd-cgi/upgrade.sh endpoint, exploiting a directory traversal vulnerability to place it in a CGI-executable directory; (3) the attacker then triggers the script via a GET request to /lpar2rrd-cgi/users.sh?cmd=commandLinux, causing the target to execute the command and return the output. The exploit requires the attacker to specify the target's IP, port, and protocol. The repository includes a README with usage instructions and references to the CVE. The main exploit logic is contained in exploit.c, with the payload written in Perl. No hardcoded IPs or domains are present; the exploit is designed to be used against arbitrary vulnerable targets specified by the user.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.