CVE-2026-22355
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in gregmolnar Simple XML Sitemap simple-xml-sitemap allows Stored XSS.This issue affects Simple XML Sitemap: from n/a through <= 1.3.
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 confidenceThis is a CSRF vulnerability in the Simple XML Sitemap WordPress plugin that enables Stored XSS attacks. Attackers can exploit the lack of anti-CSRF protection to trick authenticated administrators into submitting malicious requests that inject persistent JavaScript code into sitemap output. When other users access the generated sitemap, the stored XSS executes in their browsers.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Simple XML Sitemap plugin is installedCheck the WordPress plugins directory for the simple-xml-sitemap folder, or look for the plugin in wp-admin > Plugins. Retrieve the version number from the plugin header in the main PHP file (usually in plugins/simple-xml-sitemap/ or similar)Affected if The plugin is installed and no anti-CSRF nonce verification is implemented on state-changing admin actions
-
Identify the plugin versionOpen the main plugin file and locate the Version header in the plugin comment block, or check readme.txt for the stable tagAffected if The installed version has not been patched for CSRF protection (compare your version to the affected ranges if known)
-
Inspect admin forms for nonce fieldsView the page source of the plugin admin settings page. Look for input fields with type='hidden' containing '_wpnonce' or 'nonce' in the name attribute on all forms that change settingsAffected if Forms lack nonce fields or the submitted nonce is not verified server-side when processing settings changes
-
Verify sitemap output escapingGenerate a sitemap using the plugin (usually at /sitemap.xml or similar). View the raw XML output and check if content in URL elements is properly escaped (look for < > & etc. instead of raw < > characters)Affected if The sitemap XML contains unescaped user-supplied content that could execute as JavaScript when viewed in a browser
-
Check if plugin settings allow external form submissionsTest whether the plugin admin endpoint accepts POST requests without requiring a valid nonce token. This requires examining the PHP handler that processes the form submissionAffected if The form handler does not call wp_verify_nonce() or check_admin_referer() before saving changes
A user is affected if the Simple XML Sitemap plugin is installed and its admin forms lack anti-CSRF nonce protection, allowing stored XSS injection into sitemap output.
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 dataImplement anti-CSRF tokens (nonces) on all state-changing forms and AJAX actions, and apply proper output escaping/sanitization on all sitemap-generated content to prevent XSS execution.
- 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-22355 — 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-22355 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