CVE-2024-32814
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 Zorem Advanced Local Pickup for WooCommerce.This issue affects Advanced Local Pickup for WooCommerce: from n/a through 1.6.1.
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 vulnerability in the Advanced Local Pickup for WooCommerce plugin by Zorem. The issue allows unauthorized users to access certain functionality or data that should require proper authentication or privilege checks. The specific affected endpoints or functions are not detailed in the available description.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 plugin installationCheck if the Advanced Local Pickup for WooCommerce plugin is installed by looking for its directory in wp-content/plugins (typically named 'advanced-local-pickup-for-woocommerce' or similar) or by viewing the installed plugins in the WordPress admin under Plugins.Affected if The plugin is present in the WordPress installation
-
Identify installed plugin versionAccess the WordPress admin panel, navigate to Plugins > Installed Plugins, and locate the Advanced Local Pickup for WooCommerce plugin to read its version number. Alternatively, check the main plugin PHP file (usually in the plugin directory) for the 'Version' header in the plugin comment block.Affected if The displayed version is below 1.6.2 (the fixed version) or if the version cannot be determined (older unversioned releases)
-
Compare version against fixed releaseCompare the identified version number to 1.6.2. Versions below 1.6.2 are considered affected by this authorization vulnerability.Affected if The installed version is lower than 1.6.2
-
Review accessible endpoints (optional context)Since this is a missing authorization vulnerability and the specific endpoints are not detailed, inspect the plugin settings and any AJAX or REST API endpoints it registers. Look for actions that should require authentication (such as those in admin-ajax.php) and test whether they execute without a valid nonce or proper user capability checks.Affected if The plugin allows unauthenticated or low-privilege users to access functionality that should require higher privileges or valid nonces
You are affected if the Advanced Local Pickup for WooCommerce plugin is installed and its version is below 1.6.2.
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 to the latest version of Advanced Local Pickup for WooCommerce (version 1.6.2 or later) which contains the authorization fix. Review user roles and permissions within WooCommerce as a secondary hardening measure.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32814 — 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-32814 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