dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-4672

HIGH · 8.8 CVSS v3.1 Published 2025-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Offsprout Page Builder plugin for WordPress is vulnerable to privilege escalation in versions 2.2.1 to 2.15.2 due to improper authorization placed on the permission_callback() function. This allows authenticated attackers with Contributor-level access and above to read, create, update, or delete any user metadata, including modifying their own wp_capabilities to administrator-level privileges.

MitigationUpdate the Offsprout Page Builder plugin to version 2.15.3 or later to remediate the authorization bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Offsprout Page Builder plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Offsprout Page Builder' in the list of active plugins, or check the plugins directory via file system for /wp-content/plugins/offsprout-page-builder/
    Affected if The Offsprout Page Builder plugin is present and active in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on 'View details' for Offsprout Page Builder to see the version number, or read the main plugin file header in /wp-content/plugins/offsprout-page-builder/offsprout.php for the 'Version' field
    Affected if The installed version falls within 2.2.1 through 2.15.2 (inclusive)
  3. Check for unexpected administrator accounts
    Navigate to Users > All Users in WordPress admin. Review the list for administrator accounts that were created recently or that you do not recognize, particularly accounts that may have been created by users with Contributor-level permissions
    Affected if There are administrator accounts that were not created by existing administrators or that correspond to Contributor-level users who should not have admin privileges
  4. Audit wp_capabilities metadata for unauthorized changes
    Query the wp_usermeta table for records where meta_key = 'wp_capabilities' and meta_value contains 'administrator', cross-reference with legitimate administrator user IDs to identify any that were modified by non-administrators. Alternatively, use a plugin or WP-CLI: wp user list --role=administrator --allow-root to compare against expected admin users
    Affected if There are administrator-level wp_capabilities entries for users who should not have that role, indicating potential privilege escalation
  5. Review capability modification events in audit logs
    If audit logging is enabled (via WordPress security plugins or server logs), search for events involving updates to wp_capabilities or user_role metadata, particularly those initiated by users with Contributor or Author roles
    Affected if Audit logs show user metadata modifications performed by users lacking administrator privileges

A WordPress site is affected if it has Offsprout Page Builder installed with version 2.2.1 through 2.15.2 AND either unauthorized administrator accounts exist or capability modifications were performed by low-privileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Offsprout Page Builder plugin to version 2.15.3 or later to remediate the authorization bypass vulnerability.

Recommended fix High confidence

Latest version available on wordpress.org (version above 2.15.2)

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the 'Offsprout Page Builder' plugin in the list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the version number reflects the latest release.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4672 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4672 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data