# CVE-2025-4672: Privilege escalation in Offsprout Page Builder

> Authenticated contributors can escalate privileges to administrator by manipulating user meta due to improper authorization checks in the Offsprout Page Builder plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 31 May 2025
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-fvwx-hjg7-fmc3

## What is CVE-2025-4672?

CVE-2025-4672 is a high-severity vulnerability in Offsprout Page Builder, published on 31 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Offsprout Page Builder plugin for WordPress is vulnerable to Privilege Escalation due to improper authorization placed on the permission_callback() function in versions 2.2.1 to 2.15.2. This makes it possible for authenticated attackers, with Contributor-level access and above, to read, create, update or delete any user meta, including flipping their own wp_capabilities to administrator and fully escalate their privileges.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2025-4672 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4672 is a high-severity vulnerability in Offsprout Page Builder, published on 31 May 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-4672 in the wild and no public exploit code.

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

## Sources

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

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