dbcve.org
Easy Google MapsWordPress extension · Supsystic

CVE-2023-33926

HIGH · 8.8 CVSS v3.1 Published 2023-05-28
Fix available
A fix is available. Upgrade to 1.11.8 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Supsystic Easy Google Maps plugin <= 1.11.7 versions.

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

A Cross-Site Request Forgery (CSRF) vulnerability exists in the Supsystic Easy Google Maps WordPress plugin versions 1.11.7 and below. The plugin fails to properly validate anti-CSRF tokens (nonces) on sensitive actions, allowing attackers to trick authenticated administrators into unknowingly executing unwanted commands such as modifying plugin settings or creating malicious map configurations.

MitigationUpdate the Supsystic Easy Google Maps plugin to a version newer than 1.11.7, which should include proper nonce validation for all state-changing operations. If no update is available, implement additional server-side CSRF protections such as checking referer headers or implementing custom token validation.

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
Easy Google MapsWordPress extension
Affected:< 1.11.8

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Locate the plugin installation
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'Supsystic Easy Google Maps' or 'easy-google-maps'. Note the plugin directory name if visible.
    Affected if The plugin is installed and active in the WordPress environment
  2. Identify the installed version
    In the Plugins list, locate the Supsystic Easy Google Maps entry and read the version number displayed below the plugin name. Compare this against version 1.11.8.
    Affected if The installed version is 1.11.7 or lower (any version below 1.11.8)
  3. Verify admin access to plugin features
    Log into the WordPress admin panel and navigate to the plugin settings page (usually under a menu item labeled Google Maps or Supsystic). Confirm you can access configuration options that modify plugin settings.
    Affected if An authenticated administrator can access and modify plugin settings without additional CSRF protection checks
  4. Inspect for nonce validation in plugin actions
    If you have access to the plugin source files, examine the PHP files handling form submissions (typically in the admin folder). Look forwp_nonce_verify(), wp_verify_nonce(), or check_admin_referer() calls on state-changing functions.
    Affected if No nonce validation is found on sensitive admin actions such as saving settings or creating map configurations

You are affected if the Supsystic Easy Google Maps plugin is installed with version 1.11.7 or below and your administrators can access sensitive plugin settings without CSRF token validation.

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
Upgrade available Upgrade to 1.11.8 or later
Fixed in 1.11.8
Interim mitigation

Update the Supsystic Easy Google Maps plugin to a version newer than 1.11.7, which should include proper nonce validation for all state-changing operations. If no update is available, implement additional server-side CSRF protections such as checking referer headers or implementing custom token validation.

Recommended fix Moderate confidence

Easy Google Maps version 1.11.8

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Easy Google Maps plugin by Supsystic
  4. Check if the current version is below 1.11.8
  5. If vulnerable, click 'Update Now' to update to version 1.11.8
  6. Verify the update completed successfully by checking the plugin version

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

Fix this in Easy Google Maps Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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