dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-11894

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Shelf Planner plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on several REST API endpoints in all versions up to, and including, 2.8.1. This makes it possible for unauthenticated attackers to modify several of the plugin's settings like the ServerKey and LicenseKey.

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 Shelf Planner WordPress plugin has REST API endpoints that lack proper capability checks, allowing unauthenticated attackers to bypass authorization and modify sensitive plugin settings including ServerKey and LicenseKey through direct API calls.

MitigationUpdate Shelf Planner plugin to version 2.8.2 or later which contains the security fix. Until then, consider disabling the plugin or restricting API access at the web server level.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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 if Shelf Planner plugin is installed
    Check WordPress plugins directory or run 'wp plugin list --search="shelf-planner"' via WP-CLI, or inspect the plugin header in the main plugin file within /wp-content/plugins/
    Affected if Plugin is found and active in the WordPress installation
  2. Determine the installed plugin version
    Read the version from the plugin's main PHP file header (look for 'Version: x.x.x') or use WordPress admin plugin page
    Affected if Installed version is lower than 2.8.2 (versions before the security fix)
  3. Verify REST API endpoint exposure
    Send a GET request to the plugin's REST API endpoint (typically /wp-json/shelf-planner/ or similar) without providing authentication credentials
    Affected if API endpoint responds without requiring authentication
  4. Check for sensitive setting modification access
    Attempt a POST/PUT request to the plugin's settings API endpoint (such as /wp-json/shelf-planner/v1/settings or /wp-json/shelf-planner/settings) without authentication, looking for ability to modify ServerKey or LicenseKey fields
    Affected if Unauthenticated requests can modify or access license and server key settings

User is affected if the Shelf Planner plugin is installed with a version lower than 2.8.2 AND the REST API endpoints are accessible without authentication

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 Shelf Planner plugin to version 2.8.2 or later which contains the security fix. Until then, consider disabling the plugin or restricting API access at the web server level.

Recommended fix Moderate confidence

Latest version after 2.8.2 (check wordpress.org for current stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Shelf Planner plugin
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, download the latest version from wordpress.org and upload it manually via Plugins > Add New > Upload Plugin
  6. After updating, verify that the plugin functions correctly and settings are intact
Caveat Review plugin changelog for any settings or feature changes between your current version and the new version

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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