dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-54735

HIGH · 8.8 CVSS v3.1 Published 2025-08-20
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
Incorrect Privilege Assignment vulnerability in Imran Tauqeer CubeWP cubewp-framework allows Privilege Escalation.This issue affects CubeWP: from n/a through <= 1.1.24.

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 · moderate confidence

The CubeWP framework plugin for WordPress contains an Incorrect Privilege Assignment vulnerability (CWE-266) that allows authenticated users to escalate their privileges beyond what their assigned role should permit. This enables lower-privileged users (such as subscribers or contributors) to gain administrative access or perform actions reserved for higher-privileged roles.

MitigationUpdate CubeWP framework to the latest version beyond 1.1.24 which should contain the privilege assignment fix. Until then, limit user registration or audit existing user accounts with elevated roles.

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 CubeWP framework plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'CubeWP Framework' or check the wp-content/plugins/cubewp-framework directory exists. Alternatively, use WP-CLI: wp plugin list --name='cubewp-framework'
    Affected if CubeWP Framework plugin is installed and active
  2. Determine installed CubeWP version
    In WordPress admin, go to Plugins > Installed Plugins > CubeWP Framework and view the version number. Alternatively, check the plugin's main PHP file header or readme.txt for the 'Version' field, or use WP-CLI: wp plugin get cubewp-framework --field=version
    Affected if Version is 1.1.24 or earlier (versions beyond 1.1.24 contain the fix)
  3. Confirm user registration is enabled
    In WordPress admin, go to Settings > General and check 'Membership: Anyone can register' is checked. Alternatively, check the 'users_can_register' option in wp_options table or via WP-CLI: get_option('users_can_register')
    Affected if User registration is enabled and lower-privileged users (subscribers, contributors) exist in the system
  4. Audit user accounts for unexpected administrative roles
    In WordPress admin, go to Users and review the role column for each account. Look for users registered with subscriber or contributor roles who now have administrator capabilities. Alternatively, use WP-CLI: wp user list --role=administrator and cross-reference with expected admin accounts
    Affected if There are users with administrative roles who should not have such access based on their original registration role

Your environment is affected if the CubeWP Framework plugin version is 1.1.24 or earlier AND user registration is enabled with accounts that may have gained elevated privileges.

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 CubeWP framework to the latest version beyond 1.1.24 which should contain the privilege assignment fix. Until then, limit user registration or audit existing user accounts with elevated roles.

Recommended fix Moderate confidence

CubeWP Framework version higher than 1.1.25 (latest available version from official WordPress repository or CubeWP vendor)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the CubeWP Framework plugin (cubewp-framework)
  4. 4. Check the current installed version is 1.1.24 or lower
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest patched version
  6. 6. Verify the update completed successfully
  7. 7. Test that the plugin functionality remains intact after update
Caveat Review plugin changelog for any breaking changes between your current version and the updated version

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54735 — 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-54735 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