CVE-2026-39674
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Manoj Kumar MK Google Directions google-distance-calculator allows DOM-Based XSS.This issue affects MK Google Directions: from n/a through <= 3.1.1.
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 confidenceDOM-based Cross-site Scripting (XSS) vulnerability in the MK Google Directions (google-distance-calculator) plugin allows remote attackers to inject malicious JavaScript through unsanitized user input that gets dynamically rendered into the page DOM without proper encoding.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationCheck for the 'google-distance-calculator' or 'mk-google-directions' plugin directory in wp-content/plugins/ on the WordPress server filesystemAffected if The plugin directory exists on the server
-
Identify installed versionOpen the main plugin PHP file (usually named similarly to the plugin slug) and locate the version string in the plugin header comment, or check readme.txt for the 'Stable tag' versionAffected if The reported version is 3.1.1 or lower
-
Confirm plugin is activeLog into WordPress admin dashboard and navigate to Plugins > Installed Plugins, or query the wp_options table for the active_plugins option to check if the plugin is enabledAffected if The plugin shows as active or is present in the active plugins list
-
Check for vulnerable front-end outputView the source of any page on the site that may use the plugin's distance calculator functionality and inspect whether user-supplied parameters (such as origin/destination inputs) are reflected in the HTML without encodingAffected if The plugin reflects input parameters directly into the page DOM without sanitization
A user is affected if the MK Google Directions plugin version 3.1.1 or lower is installed and active on their WordPress site, enabling the DOM-based XSS to execute when user-supplied input is processed.
Generated from the published advisory. Verify against your own configuration.
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 dataIdentify and sanitize all client-side input sinks (document.write, innerHTML, eval, etc.) in the plugin; implement context-aware output encoding or use a sanitization library like DOMPurify before reflecting input into the DOM.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-39674 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39674 in production — separate from our analysis above.
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.
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.
- 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