Loading vulnerability…
Pwndoc v0.5.3 contains a vulnerability in the /api/audits component that allows an attacker to escalate privileges and execute arbitrary code by uploading a specially crafted audit file. The vulnerability arises from insufficient validation or sanitization of uploaded files, enabling attackers to inject and execute malicious code on the server.
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 working exploit for CVE-2022-45771, a Local File Inclusion (LFI) to Remote Code Execution (RCE) vulnerability in PwnDoc. The main exploit script, 'CVE-2022-45771-Pwndoc-LFI-to-RCE.py', is a Python3 proof-of-concept that automates the exploitation process. It authenticates to a target PwnDoc instance using provided admin credentials, creates malicious templates and audit objects, and leverages a path traversal vulnerability to upload and execute arbitrary Node.js code on the server. The payload (by default, 'files/exploit.js') demonstrates execution of shell commands via Node.js's child_process.exec. The exploit includes cleanup routines to remove traces after execution. The repository also contains a test environment setup script and documentation. The attack vector is network-based, requiring access to the PwnDoc web API. Multiple API endpoints are targeted for authentication, object creation, exploitation, and cleanup. The exploit is operational and can be used to achieve RCE on vulnerable PwnDoc instances.
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.