dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-27427

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Dylan Kuhn Geo Mashup allows Stored XSS. This issue affects Geo Mashup: from n/a through 1.13.18.

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

Geo Mashup plugin before version 1.13.19 contains a stored cross-site scripting (XSS) vulnerability due to improper neutralization of user-supplied input during web page generation. Attackers can inject malicious JavaScript that executes when other users view the affected content.

MitigationUpgrade Geo Mashup to version 1.13.19 or later. Until patched, disable the plugin or implement content security policy headers to mitigate XSS execution.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 Geo Mashup plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Geo Mashup to see the version number. Alternatively, check the plugin main file (geo-mashup.php) for the 'Version' header.
    Affected if The installed version is older than the patched version and falls within the vulnerable range.
  2. Identify content input mechanisms
    Review which Geo Mashup features accept user-submitted location data, such as custom fields, map markers, or location search forms. Check if the plugin allows unauthenticated or low-privilege users to submit location content.
    Affected if The plugin accepts user-supplied location names, descriptions, or custom field values that are not sanitized before storage.
  3. Inspect stored database content for suspicious scripts
    Query the WordPress database (wp_postmeta and related tables) for Geo Mashup metadata containing script tags, javascript:, or event handlers (onclick, onerror, etc.). Use SQL: SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%' OR meta_value LIKE '%javascript:%'.
    Affected if Any Geo Mashup-related meta entries contain unsanitized HTML or script tags.
  4. Review page output for missing output escaping
    View the source of a page displaying Geo Mashup content (map markers, location lists). Examine whether location names, descriptions, or custom field values are rendered with proper escaping (htmlspecialchars or similar).
    Affected if User-supplied location data appears in the HTML output without encoding or escaping.

A user is affected if Geo Mashup is installed with a vulnerable version, accepts user-submitted location data, and outputs that data without proper sanitization, allowing stored scripts to execute when other users view the content.

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

Upgrade Geo Mashup to version 1.13.19 or later. Until patched, disable the plugin or implement content security policy headers to mitigate XSS execution.

Recommended fix Moderate confidence

Geo Mashup version 1.13.19 or latest available release

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Geo Mashup plugin
  4. Check if an update is available and apply it, or manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  5. Verify the plugin was updated to the latest version after completion

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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