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

CVE-2026-39654

MEDIUM · 5.9 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/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 Ashish Ajani WP Simple HTML Sitemap wp-simple-html-sitemap allows DOM-Based XSS.This issue affects WP Simple HTML Sitemap: from n/a through <= 3.8.

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

DOM-based XSS vulnerability in WP Simple HTML Sitemap plugin allows injection of malicious scripts via unsanitized user input that gets rendered directly into the HTML page in the browser without server-side validation.

MitigationImplement proper output encoding in the JavaScript code that handles user input before inserting it into the DOM. Validate and sanitize all inputs client-side before rendering.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 WP Simple HTML Sitemap plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate 'WP Simple HTML Sitemap' in the list, or check the plugin directory /wp-content/plugins/ for a folder named 'simple-html-sitemap' or similar.
    Affected if The plugin is installed and active in WordPress.
  2. Check installed plugin version
    In the WordPress Plugins admin page, click the plugin name or view the plugin headers in the main PHP file (e.g., simple-html-sitemap.php) to read the 'Version' declared in the plugin metadata comment block.
    Affected if The version number is lower than 3.8, or the version cannot be determined (plugin is outdated).
  3. Identify sitemap configurations using user input
    Navigate to the plugin settings page in WordPress admin (under Settings > HTML Sitemap or similar). Review any fields where you can add custom URLs, labels, or text that may be rendered into the sitemap page.
    Affected if The plugin has any configuration options that accept custom user-supplied text, URLs, or content that gets inserted into the sitemap output.
  4. Inspect plugin JavaScript for DOM manipulation without encoding
    Locate the plugin's JavaScript files in /wp-content/plugins/simple-html-sitemap/js/ or similar. Open each .js file and search for patterns like innerHTML, document.write, or direct DOM insertion methods (e.g., createElement + appendChild) that use variables from PHP echo statements or AJAX responses.
    Affected if JavaScript code directly inserts values into the DOM using innerHTML or similar methods without visible encoding functions (such as textContent, encodeURI, or escaping \< \> \& characters).
  5. Check sitemap shortcode usage on site
    Search WordPress pages, posts, and widgets for the plugin shortcode (commonly [sitemap] or [html_sitemap]) using the WordPress admin search or by querying the wp_posts table.
    Affected if The shortcode is present and rendering on any public-facing page, allowing user input to be dynamically included in the output.

You are affected if WP Simple HTML Sitemap is installed, active, and running a version below 3.8, with any configuration or shortcode that renders user-supplied content into the sitemap HTML without proper escaping.

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

Implement proper output encoding in the JavaScript code that handles user input before inserting it into the DOM. Validate and sanitize all inputs client-side before rendering.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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