Loading vulnerability…
CVE-2025-66224 affects OrangeHRM versions 5.0 through 5.7. The vulnerability is in the application's mail configuration and delivery workflow, where user-controlled values are incorporated directly into OS-level sendmail command strings without proper sanitization or constraint. This input-neutralization failure allows unintended sendmail behaviors to be triggered during email processing. As described, the flaw can be abused to cause the application to write files to the server as part of the mail-handling routine. In deployments where those files are written into web-accessible locations, the attacker can leverage the file write to place attacker-controlled content and achieve code execution. The issue is rooted in unsafe command construction in the mail-sending logic.
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.
This repository contains a Python proof-of-concept exploit for CVE-2025-66224, a remote code execution (RCE) vulnerability in OrangeHRM versions 5.0 to 5.7. The exploit works by authenticating to the OrangeHRM web application using a valid session cookie, connecting to the backend MySQL database, and injecting a malicious command into the 'sendmail_path' configuration parameter in the 'hs_hr_config' table. The exploit then triggers the execution of this command by calling the email configuration API endpoint, resulting in arbitrary command execution on the server. The script also restores the original configuration value to minimize detection. The repository consists of the main exploit script (CVE-2025-66224.py), a README.md with detailed usage instructions and technical background, and a requirements.txt listing Python dependencies. The exploit requires both web and database access, and is intended for authorized security testing only.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.