dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-47558

HIGH · 7.5 CVSS v3.1 Published 2025-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Missing Authorization vulnerability in RomanCode MapSVG mapsvg allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects MapSVG: from n/a through < 8.6.13.

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

Missing authorization vulnerability in MapSVG WordPress plugin allows attackers to access functionality that should be restricted by access control lists. The plugin fails to properly verify user permissions before executing certain operations, enabling unauthenticated or lower-privileged users to reach protected features. This broken access control issue has a CVSS base score of 7.5 (HIGH).

MitigationUpgrade MapSVG to version 8.6.13 or later to obtain the vendor's fix. Additionally, ensure all sensitive plugin functions implement proper capability checks, nonce verification, and role-based access controls.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Verify MapSVG plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for MapSVG in the list. Alternatively, check the file /wp-content/plugins/mapsvg-directory/ exists.
    Affected if MapSVG plugin is installed and active
  2. Determine installed MapSVG version
    In WordPress admin, go to Plugins > Installed Plugins, find MapSVG, and note the version number displayed. Or check the version in /wp-content/plugins/mapsvg-directory/mapsvg.php header comment.
    Affected if Version is lower than 8.6.13 (the fixed release)
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify the MapSVG plugin shows as 'Active' rather than 'Inactive'.
    Affected if MapSVG is currently active
  4. Check for exposed admin interfaces
    Access the MapSVG admin panel URL (typically /wp-admin/admin.php?page=mapsvg-config) while logged out or as a low-privilege user (subscriber role). Verify if the interface loads without authentication prompt.
    Affected if Admin interface loads for unauthenticated or subscriber-level users (unauthorized access succeeds)

Environment is affected if MapSVG plugin version is below 8.6.13 AND the plugin is active AND unauthenticated or low-privilege users can access protected admin functionality.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MapSVG to version 8.6.13 or later to obtain the vendor's fix. Additionally, ensure all sensitive plugin functions implement proper capability checks, nonce verification, and role-based access controls.

Recommended fix High confidence

MapSVG 8.6.13 or later

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Update MapSVG plugin to version 8.6.13 or later.
  3. 3. Verify the update was successful by checking the plugin version in WordPress admin.
  4. 4. Test that the map functionality works correctly after the update.

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47558 — 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-47558 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