MappressWordPress extension · Mappresspro
CVE-2020-12675
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 · uneditedThe mappress-google-maps-for-wordpress plugin before 2.54.6 for WordPress does not correctly implement capability checks for AJAX functions related to creation/retrieval/deletion of PHP template files, leading to Remote Code Execution. NOTE: this issue exists because of an incomplete fix for CVE-2020-12077.
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 confidenceThe MapPress Google Maps for WordPress plugin before version 2.54.6 failed to properly enforce capability checks on AJAX functions that handle PHP template file operations (create/retrieve/delete). This authorization flaw allowed authenticated attackers to manipulate PHP template files, leading to remote code execution. The vulnerability is an incomplete fix for CVE-2020-12077.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
MappressWordPress extension
< 2.54.6CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 MapPress plugin is installedCheck the WordPress plugins directory or use wp-cli: wp plugin list --name=mappress or inspect /wp-content/plugins/mappress/ for the main plugin fileAffected if MapPress plugin is present in the WordPress installation
-
Determine installed MapPress versionRead the plugin header in mappress.php or mappress-google-maps-for-wordpress.php file: grep -i 'Version:' /wp-content/plugins/mappress*/mappress.phpAffected if Version is displayed as less than 2.54.6
-
Check if user authentication is required for AJAX template operationsInspect the AJAX handlers in the plugin for add_action('wp_ajax_...') calls related to template operations. Verify that capability checks (current_user_can or similar) are present before file operationsAffected if AJAX endpoints for template create/retrieve/delete do not verify user capabilities or verify capabilities incorrectly (the fix for CVE-2020-12077 was incomplete)
-
Verify PHP template files exist and are writableCheck /wp-content/uploads/mappress/ or similar directories for .php template files and their file permissionsAffected if Template files exist and are externally accessible/writable without proper authorization checks
A user is affected if the MapPress plugin version is below 2.54.6 AND the AJAX endpoints handling PHP template operations lack proper capability verification, allowing authenticated users to manipulate template files.
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.
From vendor data2.54.6
Upgrade the MapPress Google Maps for WordPress plugin to version 2.54.6 or later, which implements proper capability verification on all AJAX endpoints handling template files.
Fix this in Mappress
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12675 — 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-2020-12675 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