dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-26549

HIGH · 7.1 CVSS v3.1 Published 2025-02-13
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
Cross-Site Request Forgery (CSRF) vulnerability in pa1 WP Html Page Sitemap wp-html-page-sitemap allows Stored XSS.This issue affects WP Html Page Sitemap: from n/a through <= 2.2.

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

CSRF vulnerability in the WP Html Page Sitemap WordPress plugin (versions <=2.2) allows authenticated administrators to be tricked into submitting malicious requests that inject stored XSS payloads into sitemap settings. The attack achieves high severity because the injected scripts persist and execute for all users viewing the sitemap.

MitigationUpdate the plugin to the latest patched version once released, or disable/remove the plugin if no patch is available. Audit affected installations for existing XSS injections.

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. Confirm WP Html Page Sitemap plugin is installed
    Log in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'WP Html Page Sitemap' or 'HTML Page Sitemap' in the list of active and inactive plugins.
    Affected if The plugin appears in the installed plugins list, regardless of activation status.
  2. Check installed plugin version
    In the Plugins list, locate WP Html Page Sitemap and view the version number displayed below the plugin name. Alternatively, inspect the plugin header in /wp-content/plugins/wp-html-page-sitemap/wp-html-page-sitemap.php to read the 'Version' field.
    Affected if The version number is 2.2 or lower (e.g., 2.2, 2.1, 2.0, 1.x).
  3. Identify sitemap settings storage location
    Access WordPress database via phpMyAdmin or wp-cli. Look in the wp_options table for options containing 'sitemap' in the option_name field, such as 'html_sitemap_settings', 'html_page_sitemap_options', or similar configuration entries.
    Affected if Sitemap configuration options exist in the wp_options table.
  4. Inspect sitemap settings for malicious scripts
    Query the sitemap options from the wp_options table and examine the option_value field. Look for suspicious patterns including <script> tags, javascript: URIs, event handlers (onclick, onerror, onload), or encoded payloads that may attempt XSS injection.
    Affected if The option_value contains any script injection payloads, unexpected HTML tags, or encoded JavaScript that was not intentionally configured by an administrator.
  5. Check sitemap page output for injected scripts
    Visit the published sitemap URL (typically /html-sitemap/ or /sitemap/) in a browser and view the page source. Search for any unexpected JavaScript execution, foreign script tags, or suspicious inline event handlers.
    Affected if The rendered sitemap page contains injected JavaScript or HTML that was not added through legitimate plugin settings.

A user is affected if the WP Html Page Sitemap plugin is installed at version 2.2 or lower, or if the sitemap settings in the database contain unauthorized script injections.

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 the plugin to the latest patched version once released, or disable/remove the plugin if no patch is available. Audit affected installations for existing XSS injections.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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