dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-10896

HIGH · 8.8 CVSS v3.1 Published 2025-11-04
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
Multiple plugins for WordPress with the Jewel Theme Recommended Plugins Library are vulnerable to Unrestricted Upload of File with Dangerous Type via arbitrary plugin installation in all versions up to, and including, 1.0.2.3. This is due to missing capability checks on the '*_recommended_upgrade_plugin' function which allows arbitrary plugin URLs to be installed. This makes it possible for authenticated attackers with subscriber-level access and above to upload arbitrary plugin packages to the affected site's server via a crafted plugin URL, which may make remote code execution possible.

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

Multiple WordPress plugins using the Jewel Theme Recommended Plugins Library contain a critical auth bypass vulnerability in the plugin upgrade/installation functions. The *_recommended_upgrade_plugin functions lack capability checks, allowing any authenticated user with subscriber-level access or higher to trigger plugin installation from arbitrary URLs. Attackers can upload malicious plugin packages leading to remote code execution.

MitigationUpdate all affected plugins using the Jewel Theme Recommended Plugins Library to version 1.0.2.4 or later. If patches are unavailable, disable or remove affected plugins immediately and audit user roles to minimize subscriber-level accounts.

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 plugins using the Jewel Theme Recommended Plugins Library
    Search your WordPress wp-content/plugins directory for files containing 'recommended_upgrade_plugin' or references to 'Jewel Theme' library functions. Common patterns: *_recommended_upgrade_plugin and similar function names.
    Affected if Any plugin using the Jewel Theme Recommended Plugins Library is present and the *_recommended_upgrade_plugin functions exist in the codebase
  2. Check plugin versions against the fixed release
    For each identified plugin, locate its main PHP file and find the 'Version:' header in the plugin comment block. Compare your installed version to 1.0.2.4 as the patched version.
    Affected if The plugin version is lower than 1.0.2.4 or the version cannot be determined (likely vulnerable if using this library)
  3. Inspect upgrade functions for capability checks
    Open the plugin file containing *_recommended_upgrade_plugin functions and search for 'current_user_can' or 'capabilities' checks before the upgrade/installation logic. Also check for 'check_admin_referer' or nonce verification.
    Affected if The *_recommended_upgrade_plugin functions lack capability checks or nonce verification, allowing subscriber-level users to trigger them
  4. Audit WordPress user roles with subscriber access
    Go to Users > All Users in the WordPress admin and review the role column. Identify any users with 'Subscriber' role or custom roles that grant authenticated access.
    Affected if Any user with subscriber-level access or higher exists in the system, which combined with the vulnerable functions allows auth bypass
  5. Verify if plugin installation functions are exposed
    Access your site and attempt to trace if the upgrade functions are reachable via wp-admin/admin-ajax.php or similar endpoints. Check if the functions accept a URL parameter for plugin sources.
    Affected if The upgrade functions accept arbitrary URLs for plugin sources without validation, enabling remote plugin installation

You are affected if any WordPress plugin using the Jewel Theme Recommended Plugins Library is installed with a version before 1.0.2.4 and the *_recommended_upgrade_plugin functions lack proper capability checks, especially if subscriber-level user accounts exist.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update all affected plugins using the Jewel Theme Recommended Plugins Library to version 1.0.2.4 or later. If patches are unavailable, disable or remove affected plugins immediately and audit user roles to minimize subscriber-level accounts.

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-10896 — 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-10896 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