CVE-2025-24742

4.3 MEDIUM

📋 TL;DR

A Cross-Site Request Forgery (CSRF) vulnerability in WP Go Maps WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions. This affects all WordPress sites running WP Go Maps versions up to 9.0.40. The vulnerability enables attackers to modify plugin settings or perform other administrative actions without the victim's consent.

💻 Affected Systems

Products:
  • WP Go Maps (formerly WP Google Maps) WordPress plugin
Versions: All versions through 9.0.40
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires attacker to trick authenticated administrator into visiting malicious page while logged into WordPress admin.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could modify map configurations, inject malicious content, or potentially chain with other vulnerabilities to compromise the WordPress site.

🟠

Likely Case

Attackers trick administrators into changing plugin settings, potentially disrupting map functionality or injecting unwanted content.

🟢

If Mitigated

With proper CSRF protections and user awareness, the risk is limited to unsuccessful exploitation attempts.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

CSRF attacks are well-understood and relatively easy to execute with basic web development knowledge.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 9.0.41 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/wp-google-maps/vulnerability/wordpress-wp-google-maps-plugin-9-0-40-cross-site-request-forgery-csrf-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find WP Go Maps and click 'Update Now'. 4. Verify version is 9.0.41 or higher.

🔧 Temporary Workarounds

Temporary Plugin Deactivation

all

Disable WP Go Maps plugin until patched version is available

wp plugin deactivate wp-google-maps

CSRF Protection Headers

all

Implement Content Security Policy headers to restrict cross-origin requests

Add to .htaccess: Header set Content-Security-Policy "default-src 'self'"
Add to nginx config: add_header Content-Security-Policy "default-src 'self'";

🧯 If You Can't Patch

  • Implement strict SameSite cookie attributes for WordPress authentication cookies
  • Educate administrators about CSRF risks and safe browsing practices

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → WP Go Maps → Version. If version is 9.0.40 or lower, you are vulnerable.

Check Version:

wp plugin get wp-google-maps --field=version

Verify Fix Applied:

After updating, verify WP Go Maps version shows 9.0.41 or higher in WordPress admin plugins page.

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed CSRF token validations in WordPress logs
  • Unexpected plugin setting changes from unusual IP addresses

Network Indicators:

  • Cross-origin requests to WordPress admin-ajax.php with plugin-specific actions
  • Requests lacking proper referer headers or CSRF tokens

SIEM Query:

source="wordpress.log" AND ("csrf" OR "nonce" OR "referer") AND "wp-google-maps"

🔗 References

📤 Share & Export