CVE-2024-5768
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 · uneditedThe MIMO Woocommerce Order Tracking plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'mimo_update_provider' function in all versions up to, and including, 1.0.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update shipping provider information, including adding stored cross-site scripting.
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 · high confidenceThe MIMO Woocommerce Order Tracking plugin for WordPress is vulnerable to broken access control. The 'mimo_update_provider' function lacks a capability check, allowing any authenticated user with Subscriber-level access or higher to modify shipping provider data. Attackers can exploit this to inject stored cross-site scripting (XSS) payloads into shipping provider information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm MIMO Woocommerce Order Tracking plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'MIMO Woocommerce Order Tracking' in the list. Note whether it is active or inactive.Affected if The plugin is installed and active
-
Check the installed plugin versionOn the Plugins page, click on the plugin name to view its details, or inspect the plugin header in /wp-content/plugins/mimo-woocommerce-order-tracking/mimo-order-tracking.php to find the Version field.Affected if The version is lower than 1.0.3 (or the version field cannot be verified)
-
Verify the vulnerable function exists without capability checksAccess the plugin files via FTP or file manager, then examine the file containing 'mimo_update_provider' (typically in the main plugin PHP file). Search for the function definition and verify it lacks a current_user_can() or similar capability check before processing the request.Affected if The mimo_update_provider function exists and has no capability check (no current_user_can() call before processing)
-
Confirm WordPress users with Subscriber role or higher existIn WordPress admin, go to Users > All Users and review the roles assigned. Check if any users have Subscriber, Contributor, Author, or Editor roles.Affected if There is at least one user with Subscriber-level access or higher (roles: Subscriber, Contributor, Author, or Editor)
You are affected if the MIMO Woocommerce Order Tracking plugin is active, the version is below 1.0.3, and at least one user with Subscriber-level access or higher exists on the site.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the plugin to version 1.0.3 or later, which includes proper capability checks on the affected function. Alternatively, restrict the 'mimo_update_provider' function to users with administrator-level permissions until the patch can be applied.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5768 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5768 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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