Loading vulnerability…
The wp-google-maps plugin for WordPress, prior to version 7.11.18, contains a vulnerability in includes/class.rest-api.php where field names are not sanitized before being used in a SQL SELECT statement. This allows an attacker to inject arbitrary SQL via crafted REST API requests.
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 auxiliary module targeting a SQL injection vulnerability (CVE-2019-10692) in the WordPress wp-google-maps plugin (versions 7.11.00 to 7.11.17). The module exploits a vulnerable REST API endpoint ('/wpgmza/v1/markers') by injecting SQL via the 'fields' parameter in a GET request. Upon successful exploitation, it extracts user credentials (usernames, password hashes, and emails) from the WordPress users table and stores them as loot in Metasploit. The module requires the correct WordPress table prefix to be set if it differs from the default. The code is written in Ruby and is structured as a standard Metasploit module, with clear separation of initialization, vulnerability checking, and exploitation logic.
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.