dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-13519

MEDIUM · 6.1 CVSS v3.1 Published 2026-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The SVG Map Plugin for WordPress is vulnerable to Cross-Site Request Forgery due to missing or incorrect nonce validation on multiple AJAX actions ('save_data', 'delete_data', 'add_popup'). This allows unauthenticated attackers to forge requests that can update plugin settings, delete map data, and inject malicious web scripts by tricking administrators into clicking crafted links.

MitigationImplement proper nonce verification on all AJAX actions using wp_verify_nonce() or check_ajax_referer() before processing any data. Until the patch is available, administrators should avoid clicking untrusted links and consider disabling the plugin if high-risk.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SVG Map Plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'SVG Map' or 'SVG Map Plugin' in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed version
    In the Plugins list, find the SVG Map Plugin and note the version number displayed under the plugin name. Compare this against any available security advisories or the vendor's release notes for fixed versions
    Affected if The installed version has not yet received a security patch for CVE-2025-13519
  3. Inspect AJAX action handlers for nonce validation
    Access the plugin files via FTP or file manager, navigate to the main plugin PHP file(s), and locate the AJAX handlers registered for actions 'save_data', 'delete_data', and 'add_popup'. Search for 'wp_verify_nonce', 'check_ajax_referer', or 'nonce' within these handler functions
    Affected if The AJAX handlers for these actions do not contain nonce verification calls using wp_verify_nonce() or check_ajax_referer()
  4. Verify AJAX endpoints are publicly accessible
    Send a crafted POST request to your site's /wp-admin/admin-ajax.php endpoint with action=save_data (or delete_data, add_popup) without providing a valid nonce parameter, then observe whether the server processes the request or returns an error
    Affected if The server accepts and processes the request without returning a nonce verification error
  5. Check WordPress debug logs for CSRF warnings
    If WordPress debug logging is enabled, review wp-content/debug.log for any warnings related to the SVG Map plugin AJAX actions or missing nonce validation
    Affected if Debug logs show missing or failed nonce validation for the affected AJAX actions

A user is affected if the SVG Map Plugin is installed, the installed version lacks the CVE-2025-13519 patch, and the AJAX handlers for 'save_data', 'delete_data', or 'add_popup' lack proper nonce verification logic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper nonce verification on all AJAX actions using wp_verify_nonce() or check_ajax_referer() before processing any data. Until the patch is available, administrators should avoid clicking untrusted links and consider disabling the plugin if high-risk.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13519 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13519 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data