# CVE-2026-9613: Missing authorization in Datalogics Ecommerce Delivery – Datalogics

> Authenticated subscribers can bypass authorization to modify orders, overwrite API tokens, and trigger shipping actions in the Datalogics Ecommerce Delivery plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-2m92-vwcx-jmjg

## What is CVE-2026-9613?

CVE-2026-9613 is a medium-severity missing authorization vulnerability in Datalogics Ecommerce Delivery – Datalogics, published on 19 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-9613?


## How do I fix CVE-2026-9613?

No fix has been published for CVE-2026-9613 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9613 being exploited?

There is no known exploitation of CVE-2026-9613 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9613 and fix it if it is affected.

What it is: CVE-2026-9613 is a medium-severity missing authorization vulnerability in Datalogics Ecommerce Delivery – Datalogics, published on 19 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9613 in the wild and no public exploit code.

Affected product: Datalogics Ecommerce Delivery – Datalogics. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9613/ (Markdown: https://insights.sbomify.com/CVE-2026-9613/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9613
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9613
- OSV: https://osv.dev/vulnerability/CVE-2026-9613

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9613/
Summaries are generated and may contain mistakes; the official description above is the record.