Missing AuthorizationWeakness · CWE-862

CVE-2026-7552

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-28

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

NVD · unedited

The Geo Mashup plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.13.19. 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 expose sensitive plugin configuration data, including Google Maps API keys and GeoNames service credentials, to unauthenticated attackers.

Technical summary

dbcve analysis · high confidence

The Geo Mashup WordPress plugin versions up to 1.13.19 contain an authorization bypass vulnerability that allows unauthenticated attackers to access sensitive plugin configuration data including Google Maps API keys and GeoNames service credentials.

MitigationUpdate the Geo Mashup plugin to version 1.13.20 or later to remediate the authorization bypass. If an update is unavailable, consider removing the plugin until a patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected?

dbcve checks

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

Locate the Geo Mashup plugin installation directory

Check the WordPress plugins folder at wp-content/plugins/ for a folder named 'geo-mashup' or similar. Alternatively, query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins';

Affected if The Geo Mashup plugin folder exists and the plugin is in the active plugins list
Determine the installed plugin version

Open the main plugin file (e.g., geo-mashup/geo-mashup.php) and locate the Version header in the plugin comment block, or check the readme.txt file in the plugin directory for the 'Stable tag' entry

Affected if The version listed is 1.13.19 or any version lower (e.g., 1.13.0, 1.12.x, 1.11.x)
Compare the version against the affected range

Compare your installed version number to the affected range: versions up to and including 1.13.19 are vulnerable. Version 1.13.20 and later contain the fix

Affected if The installed version is 1.13.19 or earlier, or if the version cannot be determined but the plugin is present and active
Verify exposure of sensitive configuration data

Check if the plugin exposes any REST API endpoints or direct PHP files that could be accessed without authentication. Common paths to inspect: /wp-json/geo-mashup/* or direct access to files in the plugin directory that handle configuration

Affected if Unauthenticated access to plugin configuration data is possible, as evidenced by accessible sensitive endpoints or files

You are affected if the Geo Mashup plugin is installed and active with version 1.13.19 or earlier, as this version range allows unauthenticated attackers to retrieve sensitive configuration data including Google Maps API keys and GeoNames credentials.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update the Geo Mashup plugin to version 1.13.20 or later to remediate the authorization bypass. If an update is unavailable, consider removing the plugin until a patch is released.

Have this fixed Scoped from the published advisory

Consultation1.0 h
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

5.0 hours of engineering $860

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7552 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-7552?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

Need this fixed?

Have this fixed 5 hrs · Low

Typical engagement from $860

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-7552 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References