LiveActive security incident?Get immediate response
CVE Record

CVE-2023-48743: WordPress Simply Exclude Plugin <= 2.0.6.6 is vulnerable to Cross Site Scripting (XSS)

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Paul Menard Simply Exclude allows Reflected XSS.This issue affects Simply Exclude: from n/a through 2.0.6.6.

MediumCVSS 5.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A WordPress plugin can reflect untrusted input into generated pages, creating a cross-site scripting risk if a user follows a crafted link. Business impact is usually contained, but it can affect user trust, browser-session security, and site administration workflows.

Executive priority

Treat this as a targeted WordPress hygiene issue, not an emergency breach signal. Prioritize exposed public sites and administrative WordPress environments, especially where the plugin is unnecessary or unsupported.

Technical view

CVE-2023-48743 is a CWE-79 reflected XSS issue in Paul Menard Simply Exclude through 2.0.6.6. CVSS 3.1 is 5.8 with network attack vector, high complexity, no privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites with the Simply Exclude plugin installed at version 2.0.6.6 or earlier. The provided sources do not identify affected endpoints, installation prevalence, or a confirmed fixed version.

Exploitation context

The CVE is not marked KEV, and the supplied sources do not state active exploitation. The scoring indicates exploitation requires user interaction and has high attack complexity, reducing urgency compared with unauthenticated, automated compromise paths.

Researcher notes

Evidence is limited to the CVE description, CVSS data, CWE-79 classification, and Patchstack vulnerability entry. No exploit details, affected parameter, proof of active exploitation, or fixed version are provided in the bundle.

Mitigation direction

  • Inventory WordPress sites for the Simply Exclude plugin and version.
  • Check vendor or Patchstack guidance for an official fix or replacement advice.
  • Disable or remove the plugin where it is not business-critical.
  • Limit administrative browsing from logged-in WordPress sessions until reviewed.
  • Apply compensating controls from your WordPress security stack where available.

Validation and detection

  • Confirm whether Simply Exclude is installed on each WordPress site.
  • Record plugin versions and flag any instance at 2.0.6.6 or earlier.
  • Verify whether a vendor-supported update or advisory exists.
  • Review recent WordPress security logs for suspicious link-driven admin activity.
  • Confirm remediation by retesting inventory after changes.
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-48743 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
Medium
CVSS
5.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/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
5.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L1.63.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.8Medium
CVSS 3.1 vector shape for CVE-2023-48743Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/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
Paul MenardSimply Excludesimply-exclude, n/aunaffected
Weakness

CWE details

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