Security Alert Summary
The Datalogics Ecommerce Delivery – Datalogics WordPress plugin contains an authorization bypass that affects all versions up to and including 2.6.65. Authenticated users with subscriber-level access or higher may be able to perform actions they are not authorized to, including creating or cancelling shipping orders through the integrated logistics API, modifying WooCommerce order post meta, overwriting the plugin’s stored API token, and triggering shipping notification emails.
CVE Details
- CVE ID: CVE-2026-9613
- Affected component: Datalogics Ecommerce Delivery – Datalogics plugin for WordPress
- Affected versions: All versions up to and including 2.6.65
- Published: September 19, 2026 at 9:16:35 AM
- Last modified: September 19, 2026 at 2:17:06 PM
- CVSS v3.1 base score: 4.3 (MEDIUM)
- CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Authentication / privileges / interaction: Privileges Required: LOW (authenticated user with at least subscriber-level access); User Interaction: NONE
- Primary impact: Confidentiality: NONE; Integrity: LOW; Availability: NONE
- CWE / weakness ID: CWE-862 (Missing Authorization)
Technical Details
The plugin fails to properly verify that a user is authorized to perform certain actions. As described in the vulnerability summary, authenticated users with subscriber-level access and above can use the plugin to interact with the store’s external logistics API and with WooCommerce order data. The underlying issue is a missing or insufficient authorization check in the plugin’s action handlers (referenced in the plugin’s actions.php code paths), which permits operations that should be restricted to privileged roles.
Because the plugin uses a stored authentication token to communicate with the external logistics API, unauthorized actions can cause real-world effects: creating or cancelling shipping orders via the store’s credentials. The vulnerability also permits modification of arbitrary WooCommerce order post meta, overwriting the plugin’s stored API token, and triggering shipping notification emails to customers. The CVSS assessment indicates this results in a limited integrity impact rather than confidentiality or availability loss.
How This Could Impact Your Website
Consider a typical store workflow: a site owner oversees operations, internal staff manage orders, and an external contractor or contributor updates content. If a subscriber-level account or other low-privilege account is present and the plugin is active at an affected version, an authenticated attacker with that account could take actions that affect order handling and communications. Practical consequences include unwanted or fraudulent shipping orders being created or canceled using your store’s logistics credentials, modification of order metadata that could alter fulfillment or reporting, and the sending of shipping notifications to customers that could be used for social engineering or phishing.
While the CVSS data indicates no direct confidentiality impact, the ability to trigger emails and alter order metadata can increase the risk of targeted phishing or social engineering against customers and staff. If you are unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.
Recommended Actions
- Update the affected plugin as soon as a patched version is available.
- Review and reduce unnecessary user roles and capabilities, especially for contributors and other low-privilege accounts.
- Enforce strong passwords and enable two-factor authentication for editors and administrators.
- Remove unused or unmaintained plugins from your site.
- Monitor site activity and order logs for unusual behavior, including unexpected API calls or shipping notifications.
If youd like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.
References
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.63/actions.php#L198
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.63/actions.php#L244
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.63/actions.php#L5
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.63/actions.php#L646
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.63/actions.php#L679
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.63/actions.php#L691
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.63/actions.php#L76
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.63/actions.php#L809
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.65/actions.php#L198
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.65/actions.php#L244
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.65/actions.php#L5
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.65/actions.php#L646
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.65/actions.php#L679
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.65/actions.php#L691
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.65/actions.php#L76
- https://plugins.trac.wordpress.org/browser/datalogics/tags/2.6.65/actions.php#L809
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3552733%40datalogics&new=3552733%40datalogics
- https://www.wordfence.com/threat-intel/vulnerabilities/id/c0ed27b8-dbdc-4927-8019-52a622bfbff6?source=cve