CVE-2024-43343

Order Tracking <= 3.3.11 - Missing Authorization via send_test_email()

2024-08-16 00:00
Abdi Pranata

Strategic Overview

Status
Patched in 3.3.12b
Affected Version
<= 3.3.11
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-43343
View all Order Tracking – WordPress Status Tracking Plugin vulnerabilities

At a glance

CVE-2024-43343 is a medium-severity Missing Authorization vulnerability in the Order Tracking WordPress plugin, affecting versions <= 3.3.11. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.3.12b; sites on affected versions should update now. Disclosed August 2024, reported by Abdi Pranata.

Vulnerability Overview

The Order Tracking plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the send_test_email() function in versions up to, and including, 3.3.11. This makes it possible for authenticated attackers, with subscriber-level access and above, to send test emails.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Order Tracking <= 3.3.11 carries this weakness at send_test_email(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Order Tracking the fix is 3.3.12b: builds <= 3.3.11 are affected, anything from 3.3.12b onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 3.3.12b, 3.3.13

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Order Tracking 3.3.12b closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C