Loading vulnerability…
CVE-2023-21715 is a Microsoft Office vulnerability, specifically associated with Microsoft Publisher content, that allows a security feature bypass. Microsoft classified it as a zero-day and reported active exploitation in the wild at the time patches were released in February 2023. The vulnerability has been observed in malicious Publisher files used to deliver embedded script-based payloads as part of phishing and malware delivery chains. Available reporting characterizes the issue as a bypass of an Office security control rather than a memory corruption flaw, but does not provide sufficient public detail about the exact vulnerable function or internal implementation path.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this 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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A local security feature bypass vulnerability referenced as being exploited via Ekipa publisher files in Storm-0324 infection chains to help deliver JSSLoader.
Microsoft Office security feature bypass vulnerability (described as potentially behaving like privilege escalation) that is under active exploitation.
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.