Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13519: CWE-352 Cross-Site Request Forgery (CSRF) in smjrifle SVG Map Plugin

0
Medium
VulnerabilityCVE-2025-13519cvecve-2025-13519cwe-352
Published: Wed Jan 07 2026 (01/07/2026, 08:21:51 UTC)
Source: CVE Database V5
Vendor/Project: smjrifle
Product: SVG Map Plugin

Description

CVE-2025-13519 is a Cross-Site Request Forgery (CSRF) vulnerability in the SVG Map Plugin for WordPress, affecting all versions up to 1. 0. 0. The flaw arises from missing or incorrect nonce validation on multiple AJAX actions such as 'save_data', 'delete_data', and 'add_popup'. This allows unauthenticated attackers to trick site administrators into executing unwanted actions, including modifying plugin settings, deleting map data, or injecting malicious scripts. Exploitation requires user interaction, specifically an administrator clicking a crafted link. The vulnerability has a CVSS score of 6. 1, indicating medium severity, with potential impacts on confidentiality and integrity but no direct availability impact. No known exploits are currently reported in the wild. European organizations using this plugin in WordPress environments are at risk, especially those with administrative users who might be targeted via phishing or social engineering.

AI-Powered Analysis

AILast updated: 01/14/2026, 15:40:44 UTC

Technical Analysis

CVE-2025-13519 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the SVG Map Plugin for WordPress, versions up to and including 1.0.0. The vulnerability stems from the plugin's failure to implement proper nonce validation on several AJAX endpoints, specifically 'save_data', 'delete_data', and 'add_popup'. Nonce validation is a security mechanism designed to ensure that requests are legitimate and initiated by authenticated users. Without it, attackers can craft malicious web requests that, when executed by an authenticated administrator (e.g., by clicking a malicious link), cause unauthorized changes to the plugin's settings, deletion of map data, or injection of malicious scripts. These actions compromise the confidentiality and integrity of the affected WordPress site data. The attack vector requires no prior authentication by the attacker but does require user interaction from an administrator, making social engineering or phishing a likely exploitation method. The vulnerability is network exploitable (AV:N), has low attack complexity (AC:L), requires no privileges (PR:N), but does require user interaction (UI:R). The scope is changed (S:C) because the vulnerability affects resources beyond the initially vulnerable component. The CVSS score of 6.1 reflects a medium severity level, primarily due to the potential for data manipulation and script injection, which could lead to further compromise. No patches or official fixes are currently linked, and no known exploits have been reported in the wild as of the publication date. The vulnerability is cataloged under CWE-352, which covers CSRF issues. Organizations using the SVG Map Plugin in WordPress should be aware of this risk and take immediate steps to mitigate it.

Potential Impact

For European organizations, this vulnerability poses a moderate risk to the confidentiality and integrity of web assets running WordPress with the SVG Map Plugin installed. Attackers can exploit the CSRF flaw to alter plugin settings, delete critical map data, or inject malicious scripts, potentially leading to data loss, defacement, or further compromise through cross-site scripting (XSS) chains. The requirement for administrator interaction means that phishing or social engineering campaigns could be effective attack vectors. This risk is particularly relevant for organizations with public-facing WordPress sites that utilize the SVG Map Plugin for geographic data visualization or interactive maps. The impact could extend to reputational damage, loss of user trust, and potential regulatory consequences under GDPR if personal data is compromised or manipulated. Since no known exploits are currently active, the window for proactive mitigation is open, but the medium severity score indicates that organizations should prioritize remediation to prevent exploitation.

Mitigation Recommendations

To mitigate CVE-2025-13519, organizations should implement the following specific actions: 1) Immediately audit WordPress sites for the presence of the SVG Map Plugin and identify affected versions (up to 1.0.0). 2) If available, apply official patches or updates from the plugin vendor; if no patches exist, consider disabling or removing the plugin until a fix is released. 3) Implement custom nonce validation on all AJAX endpoints related to the plugin to ensure requests are legitimate and originate from authenticated administrators. 4) Restrict AJAX actions to authenticated users with appropriate privileges, preventing unauthenticated access. 5) Enhance administrator security awareness training to recognize and avoid phishing attempts that could trigger CSRF attacks. 6) Employ web application firewalls (WAFs) with rules to detect and block suspicious AJAX requests targeting the vulnerable endpoints. 7) Monitor logs for unusual activity related to the plugin's AJAX actions to detect potential exploitation attempts early. 8) Consider isolating or sandboxing WordPress administrative interfaces to reduce exposure to CSRF attacks. These targeted measures go beyond generic advice by focusing on the specific plugin's AJAX endpoints and the attack vector involving administrator interaction.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-21T19:11:08.471Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695e1b2fa55ed4ed998cb649

Added to database: 1/7/2026, 8:37:03 AM

Last enriched: 1/14/2026, 3:40:44 PM

Last updated: 2/7/2026, 12:47:21 AM

Views: 35

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats