CVE-2025-47559
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in RomanCode MapSVG mapsvg allows Upload a Web Shell to a Web Server.This issue affects MapSVG: from n/a through < 8.7.4.
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 confidenceMapSVG plugin versions before 8.7.4 contain an unrestricted file upload vulnerability allowing attackers to upload dangerous file types, specifically web shells, directly to the web server. This enables remote code execution on the affected system.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify MapSVG plugin is installedCheck the WordPress plugins directory or wp-content/plugins folder for the mapsvg folder. In WordPress admin, go to Plugins > Installed Plugins and look for MapSVG.Affected if MapSVG plugin is present in the installation
-
Check installed MapSVG versionIn WordPress admin, go to Plugins > Installed Plugins > MapSVG and view the version number. Alternatively, check the main plugin file header in wp-content/plugins/mapsvg/mapsvg.php for the Version field.Affected if Version is lower than 8.7.4 or version number cannot be determined (indicating a potentially outdated installation)
-
Confirm file upload functionality is accessibleLog into the MapSVG admin interface and navigate to the file upload or import settings. Check if users can upload files directly through the plugin settings panel.Affected if File upload/import feature is enabled and accessible to users
-
Inspect upload directory configurationCheck the mapsvg-upload-dir setting in WordPress options table (wp_options) or in the plugin configuration file. Verify if the designated upload directory allows script execution (contains .php or other executable files).Affected if Upload directory is web-accessible and allows PHP execution, or no upload directory restriction is configured
The environment is affected if MapSVG plugin versions before 8.7.4 are installed AND the file upload feature is enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to MapSVG version 8.7.4 or later. As an interim measure, disable the file upload functionality, ensure upload directories block PHP execution, and implement strict file type validation on the server side.
MapSVG version 8.7.4 or later
- Backup the current MapSVG installation and database before proceeding with any changes
- Upgrade MapSVG to version 8.7.4 or later release
- Verify the upgrade was successful by checking the plugin/theme version number
- Confirm the file upload functionality is working correctly with legitimate file types
- Review any uploaded files on the server to ensure no malicious web shells remain from prior exploitation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47559 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47559 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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