LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51694: WordPress Embed Privacy Plugin <= 1.8.0 is vulnerable to Cross Site Scripting (XSS)

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Epiphyt Embed Privacy allows Stored XSS.This issue affects Embed Privacy: from n/a through 1.8.0.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-51694 is a stored cross-site scripting issue in the WordPress Embed Privacy plugin through version 1.8.0. An authenticated low-privileged attacker could store malicious page content that later runs in another user's browser, potentially affecting confidentiality, integrity, and availability at limited scope.

Executive priority

Treat as a moderate priority for WordPress environments, especially public or multi-author sites. It is not listed as actively exploited in the provided sources, but stored XSS can create business impact if trusted users are targeted.

Technical view

The vulnerability is CWE-79: improper neutralization of input during web page generation. CVSS 3.1 is 6.5 with network access, low complexity, low privileges required, user interaction required, and changed scope. Sources identify Epiphyt Embed Privacy package embed-privacy through 1.8.0 as affected.

Likely exposure

Exposure is limited to WordPress sites using Epiphyt Embed Privacy version 1.8.0 or earlier. The CVSS vector indicates exploitation requires an authenticated low-privileged role and another user's interaction with affected content.

Exploitation context

The source bundle does not show CISA KEV listing or public active exploitation evidence. Because this is stored XSS, risk is higher on sites with many contributors, weak account governance, or administrative users reviewing user-generated content.

Researcher notes

Evidence is limited to CVE metadata and the Patchstack vulnerability entry. The provided data does not include exploit details, a named fixed version, or vendor remediation text. Validation should focus on plugin presence, version, content review, and vendor guidance.

Mitigation direction

  • Inventory WordPress sites for Embed Privacy version 1.8.0 or earlier.
  • Check Epiphyt and Patchstack guidance for fixed releases or temporary mitigations.
  • Update, disable, or remove the plugin according to vendor guidance.
  • Limit low-privileged content editing access until remediation is confirmed.

Validation and detection

  • Verify whether the embed-privacy plugin is installed on each WordPress site.
  • Record the installed plugin version and compare it with the affected range.
  • Review editable content areas for unexpected scripts or injected markup.
  • Confirm the plugin is updated, disabled, or removed after remediation.
  • Check administrative accounts for suspicious activity around affected content.
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-51694 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
6.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
EpiphytEmbed Privacyembed-privacy, n/aunaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.