# CVE-2025-27824: Cross-site scripting in Link iframe formatter

> An attacker with content creation privileges can inject malicious scripts via the Link iframe formatter module in Backdrop CMS.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 7 Mar 2025
- **Updated:** 7 Mar 2025
- **Also known as:** GHSA-xf37-jxxr-pmvg

## What is CVE-2025-27824?

CVE-2025-27824 is a medium-severity cross-site scripting vulnerability in backdropcms Link iframe formatter, published on 7 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An XSS issue was discovered in the Link iframe formatter module before 1.x-1.1.1 for Backdrop CMS. It doesn't sufficiently sanitize input before displaying results to the screen. This vulnerability is mitigated by the fact that an attacker must have the ability to create content containing an iFrame field.

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

## Which versions are affected by CVE-2025-27824?


## How do I fix CVE-2025-27824?

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

## Is CVE-2025-27824 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27824 and fix it if it is affected.

What it is: CVE-2025-27824 is a medium-severity cross-site scripting vulnerability in backdropcms Link iframe formatter, published on 7 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27824 in the wild and no public exploit code.

Affected product: backdropcms Link iframe formatter. 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-2025-27824/ (Markdown: https://insights.sbomify.com/CVE-2025-27824/index.md)
```

## Sources

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

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