# CVE-2024-12768: Responsive iframe <= 1.2.0 - Contributor+ Stored XSS

> Contributors can inject malicious scripts via unescaped block options in the Responsive iframe plugin, leading to stored XSS attacks.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2025
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-534q-5pch-9x4r

## What is CVE-2024-12768?

CVE-2024-12768 is a medium-severity cross-site scripting vulnerability in Unknown Responsive iframe, published on 1 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Responsive iframe WordPress plugin through 1.2.0 does not validate and escape some of its block options before outputting them back in a page/post where the block is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.

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

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

It affects 1 product.


Products: Patrickpelayo Responsive Iframe.

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

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

## Is CVE-2024-12768 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-12768 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-12768 is a medium-severity cross-site scripting vulnerability in Unknown Responsive iframe, published on 1 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-12768 exists.

Affected product: Unknown Responsive iframe. 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-12768/ (Markdown: https://insights.sbomify.com/CVE-2024-12768/index.md)
```

## Sources

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

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