CVE-2019-9851 is a vulnerability in LibreOffice, specifically related to the LibreLogo programmable turtle vector graphics script. LibreLogo, when bundled with LibreOffice, can execute arbitrary Python commands embedded within a document. While previous protections (for CVE-2019-9848) blocked LibreLogo invocation from document event script handlers, a separate LibreOffice feature allowed documents to specify pre-installed scripts to execute on global script events (e.g., document-open). This allowed attackers to bypass the previous protection and execute arbitrary Python code when a document was opened, leveraging global script event handlers. The vulnerability was present in LibreOffice versions prior to 6.2.6.
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 contains a single Metasploit module: 'libreoffice_logo_exec.rb', which exploits a code execution vulnerability in LibreOffice (CVE-2019-9851) via the LibreLogo macro. The module generates a malicious ODT file ('librefile.odt') that, when opened in LibreOffice, triggers a macro event to execute arbitrary Python code. The payload is typically a Python Meterpreter reverse shell, but can be any Python code. The exploit is weaponized, allowing for easy payload customization through Metasploit. The attack vector is local, requiring the target to open the crafted ODT file. The module references a template file ('librefile.erb') for ODT generation, and is designed for both Linux and Windows platforms where LibreOffice is installed and vulnerable.
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 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.