Datalogics - Security Vulnerability (CVE-2026-9613)

CVE-2026-9613

Vulnerability CVE-2026-9613 PLUGIN datalogics MEDIUM

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.

CVE-2026-9613

MEDIUM CVSS 4.3 Published 2026-09-19 Updated 2026-09-21

AI Risk Moderate (46/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P4 Planned

Severity Band MEDIUM

CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected Components 2

Reference Links 10

AI Risk Engine Moderate (46/100)

Exploitability High

Active Exploitation No strong signal

Published Exploit Status No public exploit references

Threat Timeline

2026-09-19 CVE published and first recorded in the threat feed.
2026-09-21 Record updated with latest vulnerability metadata.
2026-09-22 AI technical context refreshed for mitigation and impact guidance.
Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated just now

AI enriched just now (2026-09-22 20:40 UTC)

Technical Summary

Potential Impact

Severity is MEDIUM (CVSS 4.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential.

Primary risk drivers: remote code execution potential

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 46/100 (Moderate, High) with priority P4 Planned. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Datalogics PLUGIN · datalogics Affected range not specified Fixed version not specified

Datalogics Ecommerce Delivery PLUGIN · datalogics-ecommerce-delivery Affected range not specified Fixed version not specified

References

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update Datalogics to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Datalogics, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Datalogics.

How do I fix it?

Update Datalogics to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Broken Access Control flaw. An attacker who exploits it can reach actions or data that should have been restricted to someone else.