# CVE-2026-3327: Authenticated DatoCMS Web Previews Plugin Iframe Injection

> Authenticated users can inject iframes to load arbitrary external resources, bypassing frontend URL restrictions in the DatoCMS Web Previews plugin.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 27 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-x8p2-g6vv-f5mr

## What is CVE-2026-3327?

CVE-2026-3327 is a medium-severity cross-site scripting vulnerability in DatoCMS Web Previews, published on 27 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Authenticated Iframe Injection in Dato CMS Web Previews plugin. This vulnerability permits a malicious authenticated user to circumvent the restriction enforced on the configured frontend URL, enabling the loading of arbitrary external resources or origins. This issue affects Web Previews < v1.0.31.

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

## Which versions are affected by CVE-2026-3327?


## How do I fix CVE-2026-3327?

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

## Is CVE-2026-3327 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3327 and fix it if it is affected.

What it is: CVE-2026-3327 is a medium-severity cross-site scripting vulnerability in DatoCMS Web Previews, published on 27 Feb 2026. 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-2026-3327 in the wild and no public exploit code.

Affected product: DatoCMS Web Previews. 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-2026-3327/ (Markdown: https://insights.sbomify.com/CVE-2026-3327/index.md)
```

## Sources

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

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