dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-10706

HIGH · 8.8 CVSS v3.1 Published 2025-10-16
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 Classified Pro theme for WordPress is vulnerable to unauthorized plugin installation due to a missing capability check in the 'cwp_addons_update_plugin_cb' function in all versions up to, and including, 1.0.14. This makes it possible for authenticated attackers, with subscriber-level access and above, to install arbitrary plugins on the affected site's server which may make remote code execution possible. Note: The required nonce for the vulnerability is in the CubeWP Framework plugin.

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 Classified Pro WordPress theme versions up to 1.0.14 lack a capability check in the 'cwp_addons_update_plugin_cb' function, allowing any authenticated user with subscriber-level permissions or higher to install arbitrary plugins. Since plugins can contain executable PHP code, this enables remote code execution. The required nonce exists in the CubeWP Framework plugin.

MitigationUpdate Classified Pro theme to version 1.1.0 or later which includes the capability check fix. Until patched, disable or restrict the vulnerable function and review user role permissions.

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. Identify Classified Pro theme version
    Navigate to Appearance > Themes in WordPress admin, or inspect the style.css file in wp-content/themes/classified-pro/ to find the version header
    Affected if Theme version is 1.0.14 or lower (the version number appears in the theme's style.css header as 'Version: x.x.x')
  2. Locate the vulnerable function
    Search the theme files for 'cwp_addons_update_plugin_cb' - typically found in includes/classified-pro-addons.php or similar addon/controller files within the theme folder
    Affected if The function cwp_addons_update_plugin_cb exists in the theme code, indicating the vulnerable feature is present
  3. Verify CubeWP Framework plugin presence
    Check Plugins > Installed Plugins in WordPress admin, or inspect wp-content/plugins/cubewp-framework/ directory for the presence of the CubeWP Framework plugin
    Affected if CubeWP Framework plugin is installed (this plugin contains the nonce used by the vulnerable function)
  4. Review user role permissions
    Navigate to Users > Roles in WordPress admin, or inspect wp-users table in the database to identify users with subscriber-level or higher roles
    Affected if Any user account exists with subscriber, contributor, author, editor, or administrator role - these roles can authenticate and trigger the vulnerable function

You are affected if Classified Pro theme version is 1.0.14 or lower, the cwp_addons_update_plugin_cb function exists in the theme, and at least one user with subscriber-level or higher access exists on the site.

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 Classified Pro theme to version 1.1.0 or later which includes the capability check fix. Until patched, disable or restrict the vulnerable function and review user role permissions.

Recommended fix High confidence

Classified Pro theme version 1.0.15 or later

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Appearance > Themes in the WordPress admin dashboard
  3. 3. Locate the Classified Pro theme
  4. 4. Update the theme to version 1.0.15 or later if an update is available
  5. 5. Verify the update was successful by checking the theme version in Appearance > Themes
  6. 6. Ensure the CubeWP Framework plugin is also updated to the latest version to address the nonce requirement mentioned in the vulnerability description
  7. 7. Test that the site functionality remains intact after the update
Caveat Minor theme updates typically have minimal breaking changes, but always test in staging first

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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