Loading vulnerability…
InvoicePlane (self-hosted invoicing application) versions 1.7.0 through 1.7.0 contain a critical remote code execution vulnerability reachable by an authenticated administrator. The issue is exploitable by chaining local file inclusion (via manipulation of the public_invoice_template setting to include an attacker-chosen local file) with log poisoning, where the attacker injects PHP code into a server log file and then forces the application to include that poisoned log file as a template. When the included log content is interpreted by PHP, the injected code executes, enabling arbitrary system command execution. InvoicePlane 1.7.1 patches the issue.
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.
public_invoice_template inputs; reduce exposure/availability of web/PHP-readable log files; and ensure logs are stored outside of web/PHP include paths and are not readable by the application where feasible.Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.