dbcve.org
Order TrackingWordPress extension · Etoilewebdesign

CVE-2024-43343

HIGH · 8.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 3.3.13 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Missing Authorization vulnerability in Etoile Web Design Order Tracking allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Order Tracking: from n/a through 3.3.12.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Missing Authorization (Broken Access Control) vulnerability in the Etoile Web Design Order Tracking WordPress plugin. The plugin fails to properly enforce Access Control Lists (ACLs) on certain functionality, allowing authenticated users (or possibly unauthenticated users depending on the attack vector) to access administrative or privileged functions they should not have access to. This could enable privilege escalation or unauthorized data access.

MitigationUpgrade to Order Tracking version 3.3.13 or later, which contains the vendor patch for this authorization flaw. If immediate patching is not possible, restrict access to the affected plugin functionality via web server-level controls or temporarily disable the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Order TrackingWordPress extension
Affected:< 3.3.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the plugin installation
    Check if the Etoilewebdesign Order Tracking plugin files exist in your WordPress installation by looking in the wp-content/plugins/ directory for a folder containing 'order-tracking' or 'etoile' in the name.
    Affected if The plugin folder is present in the plugins directory
  2. Determine the installed version
    Open the main plugin PHP file (usually the primary PHP file in the plugin folder) and locate the version number in the plugin header comment at the top, or check the readme.txt file for the 'Stable tag' entry.
    Affected if The version number found is lower than 3.3.13
  3. Verify the plugin is active
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for the Order Tracking plugin in the list and confirm whether it shows as 'Active'.
    Affected if The plugin is active and the version is below 3.3.13
  4. Check for unauthorized access potential
    Create a test by logging in with a low-privilege user account (subscriber or contributor role) and attempt to access URL paths or admin functions typically associated with the Order Tracking plugin admin pages.
    Affected if A low-privilege user can access administrative functions or data they should not be able to view

Your environment is affected if the Order Tracking plugin is installed, active, and running at a version lower than 3.3.13.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.3.13 or later
Fixed in 3.3.13
Interim mitigation

Upgrade to Order Tracking version 3.3.13 or later, which contains the vendor patch for this authorization flaw. If immediate patching is not possible, restrict access to the affected plugin functionality via web server-level controls or temporarily disable the plugin.

Recommended fix High confidence

3.3.13

  1. Log in to the WordPress admin dashboard.
  2. Navigate to Plugins > Installed Plugins.
  3. Locate the 'Order Tracking' plugin by Etoile Web Design.
  4. Click 'Update Now' to upgrade the plugin to version 3.3.13.
  5. Verify the installed version is 3.3.13 after the update completes.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Order Tracking Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43343 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data