CVE-2024-55997
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 · uneditedMissing Authorization vulnerability in webchunky Order Delivery & Pickup Location Date Time order-delivery-pickup-location-date-time-free-version allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Order Delivery & Pickup Location Date Time: from n/a through <= 1.1.0.
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 confidenceThis is a missing authorization (broken access control) vulnerability in the Order Delivery & Pickup Location Date Time WordPress plugin. The plugin fails to properly enforce authorization checks on certain functionality, allowing unauthenticated or lower-privileged users to access or manipulate delivery/pickup order data they should not have access to.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
-
Verify the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Order Delivery & Pickup Location Date Time' or check the wp-content/plugins directory for a folder containing 'order-delivery' or similar namingAffected if The plugin is installed and active in WordPress
-
Determine the installed plugin versionIn WordPress admin > Plugins, find the plugin and view the version number displayed under the plugin name, or read the main plugin PHP file header for the 'Version' tagAffected if The installed version matches or falls within the affected version range listed in the CVE database (you must compare against official CVE sources)
-
Identify exposed AJAX endpointsExamine the plugin directory for PHP files containing 'add_action("wp_ajax_' or 'wp_ajax_nopriv' hooks, which indicate publicly accessible endpointsAffected if The plugin exposes AJAX actions without proper capability checks (wp_ajax_nopriv allows unauthenticated access)
-
Review plugin capability settingsCheck the plugin settings page in WordPress admin for any access control or capability configuration options, and inspect the plugin source code for 'current_user_can' or 'capability' checks around order data functionsAffected if Sensitive order functions lack capability verification or allow access by default roles like Subscriber/Guest
You are affected if the plugin is installed AND the installed version falls within the affected version range AND the plugin processes delivery/pickup order data with missing authorization checks on its AJAX endpoints or order handling functions.
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 dataImplement proper capability checks and authorization validation on all sensitive plugin functions and AJAX endpoints to ensure only users with appropriate permissions can access or modify order data.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55997 — 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-55997 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