Loading vulnerability…
A Local File Inclusion (LFI) vulnerability exists in the Site Editor plugin for WordPress through version 1.1.1. The vulnerability is present in the ajax_path parameter of the editor/extensions/pagebuilder/includes/ajax_shortcode_pattern.php file, which fails to properly sanitize user input, allowing remote attackers to retrieve arbitrary files from the server via absolute path traversal.
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 exploit for CVE-2018-7422, a local file inclusion (LFI) vulnerability in the WordPress Site Editor plugin version 1.1.1. The main exploit file, 'CVE-2018-7422.rb', is a Ruby script that takes a target domain and a file path as arguments. It constructs an HTTP GET request to the vulnerable plugin endpoint, passing the desired file path via the 'ajax_path' parameter. If the vulnerability is present, the server responds with the contents of the specified file, allowing attackers to read arbitrary files such as '/etc/passwd'. The repository also includes a README with usage instructions and a LICENSE file. The exploit is a standalone script, not part of a larger framework, and is intended for demonstration and testing of the LFI 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.
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.