# CVE-2025-41000: Cross-Frame Scripting (XFS) in BoomCMS

> Cross-Frame Scripting in BoomCMS allows attackers to spy on users via JavaScript in older browsers, potentially leading to data theft or account takeover.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/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:** 3 Sep 2025
- **Updated:** 3 Sep 2025
- **Also known as:** GHSA-97mj-hh96-r6f4

## What is CVE-2025-41000?

CVE-2025-41000 is a low-severity cross-site scripting vulnerability in BoomCMS, published on 3 Sep 2025. 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

Cross-Frame Scripting (XFS) vulnerability in BoomCMS v9.1.4 from UXB London. XFS is a web attack technique that exploits specific browser bugs to spy on users via JavaScript. This type of attack is based on social engineering and depends entirely on the browser chosen by the user, so it is perceived as a minor threat to web application security. This vulnerability only works in older browsers.

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

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


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

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

## Is CVE-2025-41000 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41000 is a low-severity cross-site scripting vulnerability in BoomCMS, published on 3 Sep 2025. 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-41000 in the wild and no public exploit code.

Affected product: BoomCMS. 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-41000/ (Markdown: https://insights.sbomify.com/CVE-2025-41000/index.md)
```

## Sources

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

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