Loading vulnerability…
A directory traversal vulnerability exists in the Google Doc Embedder plugin for WordPress prior to version 2.5.4. The vulnerability is present in libs/pdf.php, where the 'file' parameter is not properly sanitized, allowing remote attackers to read arbitrary files on the server by supplying directory traversal sequences (..).
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.
This repository contains a single Metasploit module targeting a vulnerability (CVE-2012-4915) in the WordPress Google Document Embedder plugin (versions 2.4.6 and below). The exploit leverages an arbitrary file disclosure flaw in the plugin's pdf.php script to retrieve the wp-config.php file, extract database credentials, and connect to the MySQL server. It then resets the WordPress admin password, logs in as admin, and uses the theme editor to inject a PHP payload (backdoor) into the theme's header.php file. The payload is then triggered via an HTTP request, granting the attacker remote code execution on the server. The module is written in Ruby and is designed for use within the Metasploit framework. The main file is 'modules/exploits/unix/webapp/wp_google_document_embedder_exec.rb', and it contains all exploit logic, including endpoint interaction, credential extraction, and payload delivery.
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.