Loading vulnerability…
The Pixabay Images plugin for WordPress, prior to version 2.4, contains a vulnerability in pixabay-images.php where hostnames are not validated. This allows remote authenticated users to upload files to arbitrary locations by specifying an upload URL with a hostname other than pixabay.com.
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 targeting a vulnerability (CVE-2015-1376) in the WordPress Pixabay Images plugin version 2.3.6. The exploit abuses the plugin's failure to validate the host of a provided download URL, allowing an attacker to upload and execute arbitrary PHP code on the target server. The module sets up a web server to serve the payload, crafts a POST request to the WordPress backend to trigger the upload, and then attempts to execute the uploaded payload by guessing its filename based on the server's time. The exploit provides remote code execution as the web server user. The code is written in Ruby and is structured as a typical Metasploit exploit module, with clear separation of initialization, exploitation, and cleanup logic. The main endpoints involved are the WordPress uploads directory and the plugin's backend admin page.
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.