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

CVE-2026-42734

HIGH · 7.1 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Dylan Kuhn Geo Mashup geo-mashup allows Reflected XSS.This issue affects Geo Mashup: from n/a through <= 1.13.19.

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

Reflected XSS vulnerability in Geo Mashup WordPress plugin allows attackers to inject malicious scripts via unsanitized user input that gets reflected back in web pages. The CVSS 7.1 score indicates low attack complexity with no privileges required but user interaction needed (clicking a malicious link).

MitigationUpdate to patched version if available, or implement proper input validation and output encoding/escaping on all user-supplied parameters before rendering in HTML context.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate Geo Mashup plugin installation
    Check your WordPress installation's wp-content/plugins directory for a folder named 'geo-mashup' or similar. Also check wp-content/mu-plugins if using must-use plugins.
    Affected if The geo-mashup plugin directory exists on the server
  2. Identify installed plugin version
    Open the main plugin file (usually geo-mashup.php) and look for the version declaration in the plugin header comment, or check the readme.txt file for the 'Stable tag' entry.
    Affected if The version found is lower than the patched version (compare when patch is released)
  3. Verify plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm Geo Mashup is activated, or query the wp_options table for option_name='active_plugins' and check if geo-mashup is listed.
    Affected if The plugin shows as active in WordPress
  4. Check for exposed user input parameters
    Review pages using Geo Mashup shortcodes or templates. Test by appending a test parameter like '?test=<script>alert(1)</script>' to URLs on pages where Geo Mashup content is displayed and see if the script reflects back unescaped.
    Affected if User-supplied parameters are reflected in HTML output without encoding

You are affected if Geo Mashup plugin is installed, active, and reflects unsanitized user input back into web pages.

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 to patched version if available, or implement proper input validation and output encoding/escaping on all user-supplied parameters before rendering in HTML context.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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