Loading vulnerability…
CVE-2019-25066 is a critical vulnerability affecting Ajenti 2.1.31 in an unspecified part of the API component. According to the provided information, remote manipulation of the vulnerable API functionality can lead to privilege escalation. The exact vulnerable function or code path is not specified in the available content, but the issue is described as remotely exploitable and publicly disclosed. The vulnerability is fixed in Ajenti 2.1.32 by patch 7aa146b724e0e20cfee2c71ca78fafbf53a8767c.
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 single Metasploit module targeting a command injection vulnerability in Ajenti version 2.1.31 (CVE-2019-25066). The exploit works by injecting a command into the 'username' parameter of a POST request to the '/api/core/auth' endpoint, allowing arbitrary command execution. The default payload is a Python Meterpreter reverse shell, enabling remote code execution on the target. The module includes a check method to verify the presence and version of Ajenti by querying '/view/login/normal'. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The code is written in Ruby and is structured as a typical Metasploit exploit module.
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.
2 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.