# CVE-2024-51803: WordPress Inline Click To Tweet plugin <= 1.0.0 - Cross Site Scripting (XSS) vulnerability

> An attacker can execute arbitrary scripts in the victim's browser via DOM-based XSS in the Inline Click To Tweet WordPress plugin.

- **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:** 19 Nov 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-x3h6-m99c-xwp8

## What is CVE-2024-51803?

CVE-2024-51803 is a medium-severity cross-site scripting vulnerability in Magnetic Creative Inline Click To Tweet, published on 19 Nov 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 Magnetic Creative Inline Click To Tweet inline-click-to-tweet allows DOM-Based XSS.This issue affects Inline Click To Tweet: from n/a through <= 1.0.0.

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

## Which versions are affected by CVE-2024-51803?


## How do I fix CVE-2024-51803?

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

## Is CVE-2024-51803 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-51803 and fix it if it is affected.

What it is: CVE-2024-51803 is a medium-severity cross-site scripting vulnerability in Magnetic Creative Inline Click To Tweet, published on 19 Nov 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-2024-51803 in the wild and no public exploit code.

Affected product: Magnetic Creative Inline Click To Tweet. 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-2024-51803/ (Markdown: https://insights.sbomify.com/CVE-2024-51803/index.md)
```

## Sources

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

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