dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-67535

MEDIUM · 6.6 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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
Deserialization of Untrusted Data vulnerability in Flipper Code - WordPress Development Company WP Maps wp-google-map-plugin allows Object Injection.This issue affects WP Maps: from n/a through <= 4.8.6.

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 vulnerability is a PHP Object Injection issue caused by unsafe deserialization of untrusted data in the WP Maps (wp-google-map-plugin) WordPress plugin. An attacker can exploit this by supplying malicious serialized PHP objects, potentially leading to arbitrary code execution, file inclusion, or database manipulation depending on available classes in the plugin and WordPress ecosystem.

MitigationUpdate WP Maps plugin to the latest patched version as soon as available. If no patch exists or cannot be applied, disable and remove the plugin immediately. Consider deploying a WAF rule to block serialized object payloads as a temporary mitigation.

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

CVSS:3.1/AV:N/AC:H/PR:H/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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Maps' or 'wp-google-map-plugin'. Alternatively, check for the presence of the plugin directory at /wp-content/plugins/wp-google-map-plugin/ or similar.
    Affected if The plugin appears in the list of installed plugins.
  2. Identify the installed plugin version
    In WordPress admin, click on the WP Maps plugin to view its details, or open the main plugin file (e.g., wp-google-map-plugin.php) and look for the 'Version:' header in the plugin comments at the top of the file.
    Affected if A version number is displayed or found in the plugin file.
  3. Compare version against known affected range
    Document the exact version number found. Since no specific version range is provided in this CVE, treat any version of the WP Maps plugin as potentially affected until an official patched version is confirmed by the vendor.
    Affected if The plugin version is any version prior to an official patch release.
  4. Check for exposed deserialization entry points
    Review the plugin's publicly accessible endpoints (ajax, REST API, or front-end forms) for usage of unserialize() on user-supplied data. This requires access to plugin source code. grep for 'unserialize' within the plugin directory.
    Affected if The plugin code contains unserialize() calls processing data from $_GET, $_POST, $_REQUEST, or similar untrusted sources.
  5. Assess plugin activity and exposure
    Check web server logs or firewall logs for unusual serialized payloads targeting the site, particularly requests to /?action= or AJAX endpoints belonging to this plugin. Also verify if the plugin is network-activated in multisite or accessible on the front end.
    Affected if The plugin is active and accessible, with no WAF or other filtering blocking malicious serialized payloads.

If the WP Maps plugin is installed and active, and no patched version has been confirmed by the vendor, the environment is likely affected by this PHP Object Injection vulnerability.

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 WP Maps plugin to the latest patched version as soon as available. If no patch exists or cannot be applied, disable and remove the plugin immediately. Consider deploying a WAF rule to block serialized object payloads as a temporary mitigation.

Recommended fix Moderate confidence

Upgrade to a version newer than 4.8.6 (check WordPress plugin repository for the latest stable release)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate the 'WP Maps' (or 'WP Google Map Plugin') plugin
  4. 4. Check if the current installed version is 4.8.6 or lower
  5. 5. If vulnerable, click 'Update Now' to install the latest available version, or manually download the updated plugin from the WordPress plugin repository
  6. 6. After updating, verify the new version number reflects the update
  7. 7. Test the map functionality on your site to ensure the update did not break existing functionality
Caveat Minor or patch updates typically do not introduce breaking changes, but test thoroughly before deploying to production

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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