# CVE-2025-12518: Stored XSS in beefree.io

> Attackers can inject malicious scripts into email templates via the Social Media icon URL, leading to script execution in the preview page.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Mar 2026
- **Updated:** 18 Mar 2026
- **Also known as:** GHSA-jqjc-j9r5-4wf2

## What is CVE-2025-12518?

CVE-2025-12518 is a medium-severity cross-site scripting vulnerability in Bee Content Design Befree SDK, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

beefree.io SDK is vulnerable to Stored XSS in Social Media icon URL parameter in email builder functionality. Malicious attacker can inject arbitrary HTML and JS into template, which will be rendered/executed when visiting preview page. However due to beefree's Content Security Policy not all payloads will execute successfully.

This issue has been fixed in version 3.47.0.

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

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


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

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

## Is CVE-2025-12518 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12518 is a medium-severity cross-site scripting vulnerability in Bee Content Design Befree SDK, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-12518 in the wild and no public exploit code.

Affected product: Bee Content Design Befree SDK. 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-12518/ (Markdown: https://insights.sbomify.com/CVE-2025-12518/index.md)
```

## Sources

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

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