Wordpress Vulnerability (CVE-2025-12062)
CVE-2025-12062
The WP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.8.6 via the ...
Overview
A significant security vulnerability has been identified in the popular WP Maps plugin for WordPress. This flaw allows attackers with even minimal access to your website to read sensitive files and potentially execute malicious code on your server.
Vulnerability Explained
In simple terms, the plugin contains a function that insecurely loads template files. An attacker logged into the site with a basic “Subscriber” account can manipulate this function to force the website to include and execute a malicious .html file they have uploaded. Since .html files can contain PHP code, this allows the attacker to run any commands they wish on your web server. This type of flaw is known as Local File Inclusion (LFI).
Potential Impact
The consequences of this vulnerability are severe:
- Data Theft: Attackers can access sensitive files like
wp-config.php, which contains database credentials and secret keys. - Complete Site Compromise: By executing PHP code, an attacker can create new administrator accounts, deface your site, install backdoors, or deploy malware.
- Server Takeover: In worst-case scenarios, this could lead to a full compromise of your hosting server, affecting other sites and data.
Remediation and Mitigation Steps
Immediate action is required to protect your website.
- Update Immediately: The primary fix is to update the “WP Maps – Store Locator, Google Maps…” plugin to version 4.8.7 or higher. This update patches the vulnerability.
- Verify Update: In your WordPress admin dashboard, navigate to Plugins > Installed Plugins. Locate the WP Maps plugin and confirm its version is 4.8.7 or above.
- Restrict File Uploads: If you cannot update immediately, ensure that untrusted users cannot upload
.htmlfiles. Review any other plugins or forms that allow file uploads and restrict permitted file types to only those absolutely necessary (e.g.,.jpg,.png,.pdf). - Audit User Accounts: Review your website’s user list and remove any unnecessary or suspicious “Subscriber” accounts. Ensure all user accounts have strong, unique passwords.
- General Security Hygiene: Always keep all WordPress plugins, themes, and the core itself updated to their latest versions to mitigate known security risks.
If you suspect your site has been compromised, consider a full security audit, restore from a known-clean backup, and change all passwords (WordPress admin, database, and hosting).
Never miss a critical vulnerability
Get real-time security alerts delivered to your preferred platform.
Related Advisories
Object lifecycle issue in DevTools in Google Chrome prior to 145.0.7632.159 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a craft...
The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to SQL Injection via the 'coupon_code' parameter in all versions up to, and including, 3.9.6 due to insufficient...
The WP Mail Logging plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.15.0 via deserialization of untrusted input from the email log message field. Thi...
The RSS Aggregator plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'template' parameter in all versions up to, and including, 5.0.10 due to insufficient input sanitization...
Other Google Vulnerabilities
OpenClaw versions prior to 2026.2.14 contain a webhook routing vulnerability in the Google Chat monitor component that allows cross-account policy context misrouting when multiple webhook targets shar...
Object lifecycle issue in DevTools in Google Chrome prior to 145.0.7632.159 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a craft...