# CVE-2025-1777: The BM Content Builder plugin for WordPress is vulnerable to unauthorized modification of data to a missing capability check on the 'ux_cb_p


- **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
- **Fix available:** No
- **Published:** 6 Jun 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q9jq-f2hm-mq6f

## What is CVE-2025-1777?

CVE-2025-1777 is a medium-severity vulnerability in SeaTheme BM Content Builder, published on 6 Jun 2025. 

### Official description

The BM Content Builder plugin for WordPress is vulnerable to unauthorized modification of data to a missing capability check on the 'ux_cb_page_options_save' function in all versions up to, and including, 3.16.2.1. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-1777 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1777 is a medium-severity vulnerability in SeaTheme BM Content Builder, published on 6 Jun 2025. 
Exploitation: There is no known exploitation of CVE-2025-1777 in the wild and no public exploit code.

Affected product: SeaTheme BM Content Builder. 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-1777/ (Markdown: https://insights.sbomify.com/CVE-2025-1777/index.md)
```

## Sources

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

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