CVE-2025-13519
Unknown Unknown - Not Provided
CSRF in WordPress SVG Map Plugin Allows Unauthorized Settings Changes

Publication date: 2026-01-07

Last updated on: 2026-01-07

Assigner: Wordfence

Description
The SVG Map Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.0. This is due to missing or incorrect nonce validation on multiple AJAX actions including 'save_data', 'delete_data', and 'add_popup'. This makes it possible for unauthenticated attackers to update the plugin's settings, delete map data, and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-07
Last Modified
2026-01-07
Generated
2026-05-07
AI Q&A
2026-01-07
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
saedi svg_map_plugin to 1.0.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a Cross-Site Request Forgery (CSRF) issue in the SVG Map Plugin for WordPress (up to version 1.0.0). It occurs because the plugin's AJAX actions such as 'save_data', 'delete_data', and 'add_popup' lack proper nonce validation and user capability checks. This allows an attacker to trick an authenticated site administrator into performing unwanted actions like updating plugin settings, deleting map data, or injecting malicious scripts via forged requests. [1]


How can this vulnerability impact me? :

An attacker exploiting this vulnerability can manipulate the SVG map data by adding, deleting, or modifying map points and popups without proper authorization. This can lead to unauthorized changes in the website's content, potential injection of malicious scripts, and disruption of the site's functionality. Since the attacker relies on tricking an administrator into performing actions, it can result in compromised site integrity and possible security breaches. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring AJAX requests to the WordPress site that target the SVG Map Plugin's AJAX actions such as 'save_data', 'delete_data', and 'add_popup'. Suspicious or unauthorized POST requests to these AJAX endpoints, especially those lacking valid nonce tokens or originating from unauthenticated users, may indicate exploitation attempts. You can use network monitoring tools or web server logs to detect such requests. For example, using command-line tools like curl to simulate or check for these requests: 1. curl -X POST -d 'action=save_data&points=...' https://yourwordpresssite.com/wp-admin/admin-ajax.php 2. curl -X POST -d 'action=delete_data&point=...' https://yourwordpresssite.com/wp-admin/admin-ajax.php 3. curl -X POST -d 'action=add_popup&point=...&popup=...' https://yourwordpresssite.com/wp-admin/admin-ajax.php Additionally, inspecting web server access logs for POST requests to admin-ajax.php with these actions and no valid nonce or from unexpected IPs can help detect exploitation attempts. [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include: 1. Update the SVG Map Plugin to a version that patches this vulnerability if available. 2. If no update is available, temporarily disable or deactivate the SVG Map Plugin to prevent exploitation. 3. Implement or enforce nonce validation and user capability checks on the AJAX actions 'save_data', 'delete_data', and 'add_popup' to ensure only authorized users can perform these actions. 4. Restrict access to the WordPress admin area and AJAX endpoints to trusted IP addresses if possible. 5. Monitor logs for suspicious activity related to these AJAX actions. 6. Consider applying Web Application Firewall (WAF) rules to block unauthorized AJAX requests targeting these actions. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart