dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-12062

HIGH · 8.8 CVSS v3.1 Published 2026-02-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
The WP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.8.6 via the fc_load_template function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to include and execute arbitrary .html files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .html file types can be uploaded and included.

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 WP Maps WordPress plugin contains a Local File Inclusion vulnerability in the fc_load_template function affecting all versions up to 4.8.6. Authenticated attackers with Subscriber-level permissions can manipulate the function to include and execute arbitrary .html files containing PHP code, achieving remote code execution.

MitigationUpdate the WP Maps plugin to version 4.8.7 or later. If immediate update is not possible, restrict or disable Subscriber-level user accounts and consider temporarily disabling the plugin.

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
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 checks

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

  1. Verify WP Maps plugin is installed and identify its version
    In WordPress admin, go to Plugins > Installed Plugins and locate WP Maps. The version number is displayed in the plugin description. Alternatively, check the plugin file header in /wp-content/plugins/wp-maps/wp-maps.php for the Version field.
    Affected if The plugin is installed and the version is 4.8.6 or lower (any version up to 4.8.6 is affected).
  2. Confirm subscriber-level user accounts exist
    In WordPress admin, go to Users > All Users and review the roles assigned. Look for any accounts with the Subscriber role.
    Affected if At least one Subscriber-level account exists in the WordPress installation, providing the minimum privilege level required to exploit this vulnerability.
  3. Inspect access logs for suspicious template inclusion requests
    Review web server access logs (Apache error.log, Nginx access.log) or WordPress activity logs for requests containing 'fc_load_template' or 'template=' parameters, especially those referencing paths outside the expected template directory.
    Affected if Any logged requests to fc_load_template with manipulated template paths indicate active exploitation attempts.
  4. Check if the plugin fc_load_template function is accessible
    Examine the plugin source file (wp-maps.php or related files) to locate the fc_load_template function. Verify it accepts user-controlled input for template path inclusion without proper sanitization.
    Affected if The function accepts unsanitized template parameters and is accessible to authenticated users, including subscribers.

A user is affected if the WP Maps plugin version is 4.8.6 or lower AND at least one subscriber-level account exists in the WordPress site, allowing the LFI vulnerability to be exploited.

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

Update the WP Maps plugin to version 4.8.7 or later. If immediate update is not possible, restrict or disable Subscriber-level user accounts and consider temporarily disabling the plugin.

Recommended fix Moderate confidence

Plugin version higher than 4.8.6 (check WordPress plugin repository for latest release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin version is higher than 4.8.6
  6. 6. Test the plugin functionality to ensure the update did not break existing features
Caveat Verify map functionality and any custom templates after upgrading

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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