Printix Secure Cloud Print Management through version 1.3.1106.0 creates a temporary temp.ini file in a directory with insecure permissions. A race condition affecting this temporary-file handling can allow privilege escalation.
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 provides a proof-of-concept (POC) exploit for CVE-2022-25090, a local privilege escalation vulnerability in Printix Secure Cloud Print Management (version 1.3.1106.0 and below) on Windows. The exploit is implemented in C# (.NET Framework 4.7.2) and consists of a Visual Studio solution with the main logic in Program.cs. The exploit works by searching for the Printix installer MSI file in the C:\Windows\Installer directory, then monitoring the user's temp directory for the creation of a 'msiwrapper.ini' file. When found, it modifies the 'SetupFileName' entry in this file to point to a user-supplied payload (executable), which is then executed with SYSTEM privileges when the Printix installer runs. The exploit requires the attacker to have local access and the ability to provide a payload. The repository includes build files, configuration files, and a README with detailed usage instructions and background on the vulnerability.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.