dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-0974

HIGH · 8.8 CVSS v3.1 Published 2026-02-19
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 Orderable – WordPress Restaurant Online Ordering System and Food Ordering Plugin plugin for WordPress is vulnerable to unauthorized plugin installation due to a missing capability check on the 'install_plugin' function in all versions up to, and including, 1.20.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to install arbitrary plugins, which can lead to Remote Code Execution.

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 Orderable WordPress plugin up to version 1.20.0 lacks a capability check on its 'install_plugin' function, allowing any authenticated user with Subscriber-level access or higher to install arbitrary plugins. This privilege escalation vulnerability enables Remote Code Execution by installing malicious plugins.

MitigationAdd a capability check (e.g., current_user_can('install_plugins')) before the install_plugin function call and update to version 1.20.1 or later.

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. Check if Orderable plugin is installed
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins and look for 'Orderable' in the list, or inspect the file system at wp-content/plugins/ for a folder named 'orderable'
    Affected if The Orderable plugin is not present on the WordPress site
  2. Identify installed Orderable version
    In the plugin list view, note the version number displayed under the Orderable plugin name, or read the main plugin file header at wp-content/plugins/orderable/orderable.php and look for the 'Version:' comment
    Affected if Version is lower than 1.20.1 (the patched release)
  3. Verify AJAX endpoint accessibility for low-privilege users
    Using a browser or HTTP tool, attempt to call the AJAX action 'orderable_install_plugin' while logged in as a Subscriber-level user. Example: POST to wp-admin/admin-ajax.php with action=orderable_install_plugin
    Affected if The request does not return a 403 Forbidden or capability error, indicating the function is accessible to subscribers

A user is affected if the Orderable plugin is installed with a version below 1.20.1 and the install_plugin AJAX functionality is accessible to users with Subscriber-level access.

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

Add a capability check (e.g., current_user_can('install_plugins')) before the install_plugin function call and update to version 1.20.1 or later.

Recommended fix Moderate confidence

Orderable version > 1.20.0 (latest stable release)

  1. 1. Backup your WordPress site before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Locate the 'Orderable' plugin.
  5. 5. If an update is available, click 'Update Now' to update to the latest version.
  6. 6. If no update is shown in the admin, manually download the latest version of the Orderable plugin from the WordPress Plugin Repository (plugins.trac.wordpress.org).
  7. 7. Deactivate the current Orderable plugin.
  8. 8. Delete the current Orderable plugin files.
Caveat Review plugin settings after upgrade as minor configuration changes may occur with major version updates

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
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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