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

> An attacker can inject malicious scripts into pages via the Embed Privacy plugin, potentially compromising user sessions or site integrity.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Feb 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-283m-jhf4-68hp

## What is CVE-2023-51694?

CVE-2023-51694 is a medium-severity cross-site scripting vulnerability in Epiphyt Embed Privacy, published on 1 Feb 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2023-51694?

It affects 1 product.


Products: Epiph Embed Privacy.

## How do I fix CVE-2023-51694?

No fix has been published for CVE-2023-51694 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-51694 being exploited?

There is no known exploitation of CVE-2023-51694 in the wild and no public exploit code.

## Other vulnerabilities in Epiphyt Embed Privacy

- [CVE-2023-48300](https://insights.sbomify.com/CVE-2023-48300/): Embed Privacy missing escaping for show_all attribute in opt-out shortcode (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51694 and fix it if it is affected.

What it is: CVE-2023-51694 is a medium-severity cross-site scripting vulnerability in Epiphyt Embed Privacy, published on 1 Feb 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-51694 in the wild and no public exploit code.

Affected product: Epiphyt Embed Privacy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-51694/ (Markdown: https://insights.sbomify.com/CVE-2023-51694/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-51694
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-51694
- OSV: https://osv.dev/vulnerability/CVE-2023-51694

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-51694/
Summaries are generated and may contain mistakes; the official description above is the record.