LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46627: WordPress WP Simple HTML Sitemap Plugin <= 2.1 is vulnerable to Cross Site Scripting (XSS)

Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Ashish Ajani WordPress Simple HTML Sitemap plugin <= 2.1 versions.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-46627 affects the WordPress Simple HTML Sitemap plugin version 2.1 and earlier. An unauthenticated attacker may be able to cause malicious script to run in a victim's browser if the victim interacts with a crafted request. This is a business risk for public WordPress sites because it can affect user trust, content integrity, and session safety.

Executive priority

Treat this as a high-priority WordPress exposure if the plugin is installed. It is not proven actively exploited in the provided sources, but it is unauthenticated, public-site relevant, and can affect users or administrators through browser-side script execution.

Technical view

The issue is unauthenticated reflected cross-site scripting in Ashish Ajani's WordPress Simple HTML Sitemap plugin up to version 2.1. It is tracked as CWE-79 with CVSS 3.1 score 7.1, vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L. The source bundle does not provide parameter-level detail or a fixed version.

Likely exposure

Exposure is likely limited to WordPress sites that have the WordPress Simple HTML Sitemap plugin installed at version 2.1 or earlier. The bundle does not identify affected CPEs, WordPress core dependencies, or prevalence. Public-facing sites have higher practical exposure because reflected XSS is normally delivered through links or requests to reachable pages.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no supplied source states active exploitation. The CVSS vector indicates remote network reachability, low attack complexity, no privileges required, and required user interaction. Impact is browser-side and scoped to users who interact with a crafted request.

Researcher notes

The available evidence identifies reflected XSS but does not include root-cause detail, affected parameters, exploit maturity, or a named fixed release. Avoid assuming a patch exists from the bundle alone. Focus validation on asset inventory, version confirmation, and vendor guidance correlation.

Mitigation direction

  • Inventory WordPress sites for the wp-simple-html-sitemap plugin and installed version.
  • If version 2.1 or earlier is present, check vendor or Patchstack guidance immediately.
  • Disable or remove the plugin if no trusted fixed version is available.
  • Prioritize public sites and administrator-facing workflows for remediation review.
  • Use layered browser and WordPress hardening where available.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress property.
  • Record the exact plugin version and compare it with the affected range.
  • Review vendor, CVE, and Patchstack entries for updated remediation status.
  • Check web logs and security telemetry for unusual requests to sitemap plugin routes.
  • Validate remediation by confirming the vulnerable version is no longer active.
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-79: 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-2023-46627 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-2023-46627Attack 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
Ashish AjaniWordPress Simple HTML Sitemapwp-simple-html-sitemap, n/aunaffected
Weakness

CWE details

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