Datalogics Ecommerce Delivery Plugin up to 2.6.65 on WordPress authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.77+ |
Summary
A vulnerability has been found in Datalogics Ecommerce Delivery Plugin up to 2.6.65 and classified as critical. Impacted is an unknown function. Performing a manipulation results in authorization. This vulnerability is reported as CVE-2026-9613. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical has been found in Datalogics Ecommerce Delivery Plugin up to 2.6.65. This affects an unknown part. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The Datalogics Ecommerce Delivery – Datalogics plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.6.65. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to create and cancel real shipping orders through the external logistics API using the store's stored authentication token, modify arbitrary WooCommerce order post meta on any order, overwrite the plugin's stored API token, and trigger shipping notification emails to customers.
It is possible to read the advisory at wordfence.com. This vulnerability is uniquely identified as CVE-2026-9613 since 05/26/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/19/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-83569). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 2.6.0
- 2.6.1
- 2.6.2
- 2.6.3
- 2.6.4
- 2.6.5
- 2.6.6
- 2.6.7
- 2.6.8
- 2.6.9
- 2.6.10
- 2.6.11
- 2.6.12
- 2.6.13
- 2.6.14
- 2.6.15
- 2.6.16
- 2.6.17
- 2.6.18
- 2.6.19
- 2.6.20
- 2.6.21
- 2.6.22
- 2.6.23
- 2.6.24
- 2.6.25
- 2.6.26
- 2.6.27
- 2.6.28
- 2.6.29
- 2.6.30
- 2.6.31
- 2.6.32
- 2.6.33
- 2.6.34
- 2.6.35
- 2.6.36
- 2.6.37
- 2.6.38
- 2.6.39
- 2.6.40
- 2.6.41
- 2.6.42
- 2.6.43
- 2.6.44
- 2.6.45
- 2.6.46
- 2.6.47
- 2.6.48
- 2.6.49
- 2.6.50
- 2.6.51
- 2.6.52
- 2.6.53
- 2.6.54
- 2.6.55
- 2.6.56
- 2.6.57
- 2.6.58
- 2.6.59
- 2.6.60
- 2.6.61
- 2.6.62
- 2.6.63
- 2.6.64
- 2.6.65
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (Wordfence): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/26/2026 CVE reserved09/19/2026 Advisory disclosed
09/19/2026 VulDB entry created
09/19/2026 VulDB entry last update
Sources
Advisory: wordfence.comStatus: Not defined
CVE: CVE-2026-9613 (🔒)
GCVE (CVE): GCVE-0-2026-9613
GCVE (VulDB): GCVE-100-407907
EUVD: 🔒
Entry
Created: 09/19/2026 10:41Updated: 09/19/2026 14:07
Changes: 09/19/2026 10:41 (62), 09/19/2026 14:07 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.