dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3581

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
The Basic Google Maps Placemarks plugin for WordPress is vulnerable to authorization bypass in versions up to, and including, 1.10.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to modify stored map latitude and longitude options.

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 · moderate confidence

The Basic Google Maps Placemarks WordPress plugin fails to properly verify user authorization before allowing modifications to stored map latitude and longitude options. This authorization bypass allows unauthenticated attackers to send requests that directly modify geographic coordinate settings in the database, potentially disrupting map functionality or misplacing map markers.

MitigationUpdate the plugin to a version beyond 1.10.7 once available; until then, consider restricting access to the affected endpoints via web server configuration or temporarily disabling map configuration features if feasible.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Confirm plugin installation and version
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, locate 'Basic Google Maps Placemarks' and note the version number displayed. Alternatively, check the plugin header in /wp-content/plugins/basic-google-maps-placemarks/basic-google-maps-placemarks.php for the 'Version' comment.
    Affected if The installed version is 1.10.7 or lower (the plugin is vulnerable up to version 1.10.7).
  2. Identify accessible plugin endpoints
    Check for AJAX endpoints or admin-ajax.php hooks registered by the plugin. Search plugin PHP files for 'add_action' calls with 'wp_ajax' or 'wp_ajax_nopriv' prefixes that handle map coordinate options. Also examine any custom REST API routes if registered.
    Affected if The plugin exposes endpoints that handle map latitude/longitude options and are accessible to unauthenticated users (actions registered with 'wp_ajax_nopriv_').
  3. Test option modification without authentication
    Send a crafted POST request to the identified endpoint (commonly /wp-admin/admin-ajax.php with action parameter matching the plugin's handler) containing modified latitude/longitude values. Inspect the HTTP response and verify if the database values changed using WordPress get_option() or by reloading the map settings page.
    Affected if The server accepts and processes the request without requiring authentication and successfully modifies the map coordinate options in the database.
  4. Review access control implementation
    Examine the plugin source code for capability checks before option updates. Look for functions that handle saving map coordinates and verify if they include current_user_can() or similar authorization checks. Search for 'update_option' calls within map-related AJAX handlers.
    Affected if The code lacks proper authorization checks (no current_user_can() verification) before executing option updates.

You are affected if the Basic Google Maps Placemarks plugin is installed at version 1.10.7 or below AND unauthenticated users can successfully modify map latitude/longitude settings through exposed endpoints.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 1.10.7 once available; until then, consider restricting access to the affected endpoints via web server configuration or temporarily disabling map configuration features if feasible.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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