Loading vulnerability…
Dompdf 1.2.1 allows remote code execution when an attacker-controlled HTML input contains a CSS @font-face declaration whose src:url field references a PHP file. A reported secondary exploitation vector used the vulnerability for server-side request forgery and local file inclusion to render server-side file contents.
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 (2 hidden).
This repository provides a proof-of-concept (PoC) exploit for CVE-2022-28368, a remote code execution vulnerability in Dompdf versions prior to 1.2.1. The exploit is implemented in a single Python script (dompdf-rce.py), which automates the process of injecting malicious CSS into a vulnerable HTML-to-PDF conversion endpoint. The attack leverages Dompdf's font caching mechanism to write a base64-encoded malicious font file with a .php extension to the server's font cache directory. The script then accesses this file via the web to trigger remote code execution. The repository also includes a README with usage instructions and a requirements.txt for dependencies. The exploit requires the attacker to know or guess the vulnerable endpoints and assumes the server is configured in a way that allows web access to the font cache directory. No detection or fake code is present; this is a functional PoC exploit.
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.
1 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.