dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-2631

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Datalogics Ecommerce Delivery WordPress plugin before 2.6.60 exposes an unauthenticated REST endpoint that allows any remote user to modify the option `datalogics_token` without verification. This token is subsequently used for authentication in a protected endpoint that allows users to perform arbitrary WordPress `update_option()` operations. Attackers can use this to enable registartion and to set the default role as Administrator.

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 Datalogics Ecommerce Delivery WordPress plugin before 2.6.60 exposes an unauthenticated REST API endpoint that allows any remote attacker to modify the 'datalogics_token' option without verification. This token is subsequently used to authenticate to a protected endpoint that permits arbitrary WordPress update_option() operations, enabling attackers to enable user registration and set the default role to Administrator for full site compromise.

MitigationUpgrade to version 2.6.60 or later immediately. If immediate upgrade is not possible, disable the plugin or restrict access to the REST API endpoints 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 if the Datalogics Ecommerce Delivery plugin is installed
    Locate the plugin directory in the WordPress filesystem at /wp-content/plugins/ and look for a folder named 'datalogics-ecommerce-delivery' or similar, or check via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin directory exists in the WordPress plugins folder
  2. Determine the installed plugin version
    Open the main plugin file (usually index.php or a dedicated main PHP file) in the plugin folder and look for a version comment or constant at the top, or check the WordPress plugin admin page for the version number
    Affected if The version number is lower than 2.6.60 or no version is displayed (indicating an old installation)
  3. Verify the vulnerable REST API endpoint is accessible
    Send a GET request to /wp-json/datalogics/v1/settings or /wp-json/datalogics-ecommerce-delivery/v1/ (adjust path based on actual plugin routing) without authentication and check for a response
    Affected if The endpoint returns a valid JSON response without requiring authentication
  4. Inspect the datalogics_token option value
    Query the WordPress options table for 'datalogics_token' using a database tool or WP-CLI: wp option get datalogics_token
    Affected if A non-empty token value exists in the database (indicates the option is set and potentially exploitable)
  5. Check for signs of compromise via user registration settings
    Query WordPress options for 'users_can_register' and 'default_role' using: wp option get users_can_register && wp option get default_role
    Affected if users_can_register is set to 1 AND default_role is set to 'administrator' (indicates the attack has been performed)

If the Datalogics Ecommerce Delivery plugin is installed with a version before 2.6.60 and the REST API endpoint is accessible without authentication, the environment is affected by this CVE.

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

Upgrade to version 2.6.60 or later immediately. If immediate upgrade is not possible, disable the plugin or restrict access to the REST API endpoints at the web server level.

Recommended fix High confidence

Datalogics Ecommerce Delivery version 2.6.60 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Datalogics Ecommerce Delivery plugin
  4. If an update is available, click 'Update Now' to upgrade to version 2.6.60 or later
  5. Verify the plugin updated successfully by checking the version number
  6. Confirm that the datalogics_token option has not been tampered with by reviewing WordPress options in the database or via wp-cli: wp option get datalogics_token
  7. Enable registration and set default role through WordPress admin only if needed, rather than using the vulnerable endpoint

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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