LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22355: WordPress Simple XML Sitemap plugin <= 1.3 - CSRF to Stored XSS vulnerability

Cross-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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22355 affects the WordPress Simple XML Sitemap plugin through version 1.3. A malicious site could trick a logged-in administrator into making an unintended change that stores script in the site. That script may later run in users’ browsers. Treat this as high priority for WordPress sites using this plugin.

Executive priority

Prioritize sites running this plugin because stored XSS can affect site trust, administrator sessions, and visitors. The issue is high severity but requires user interaction, so urgency should focus on confirming exposure and applying official remediation or disabling the plugin if no fix is available.

Technical view

The issue is a CSRF vulnerability leading to stored XSS in gregmolnar Simple XML Sitemap, package simple-xml-sitemap, versions through 1.3. CVSS 3.1 is 7.1: network reachable, low complexity, no privileges required, user interaction required, scope changed, with low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress installations with Simple XML Sitemap installed at version 1.3 or earlier. Risk is highest where administrators are logged into WordPress while browsing untrusted pages. The provided sources do not identify other affected products or platforms.

Exploitation context

The CVE is not listed as KEV in the provided data, and the sources do not state active exploitation. Exploitation requires user interaction, likely involving a logged-in privileged WordPress user being induced to visit attacker-controlled content. Do not assume compromise without site-specific evidence.

Researcher notes

The source bundle identifies CSRF to stored XSS and CVSS 7.1, but gives limited implementation detail. There is an apparent metadata inconsistency: the description says through <=1.3, while the affected object lists version "0" with defaultStatus unaffected. Validate exposure against installed plugin metadata and vendor records.

Mitigation direction

  • Inventory WordPress sites for the Simple XML Sitemap plugin and version.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed release.
  • Update if an official fixed version is available.
  • If no fix is available, disable or remove the plugin where business impact allows.
  • Warn administrators not to browse untrusted sites while logged into WordPress.

Validation and detection

  • Confirm whether the plugin simple-xml-sitemap is installed.
  • Record the installed plugin version and compare it to 1.3 or earlier.
  • Review administrative pages for unexpected stored script content.
  • Check WordPress user activity around suspicious administrator sessions.
  • Monitor vendor and Patchstack pages for remediation updates.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22355 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-22355Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
gregmolnarSimple XML Sitemapsimple-xml-sitemap, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.