CVE-2025-47634
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 Keylor Mendoza WC Pickup Store wc-pickup-store allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WC Pickup Store: from n/a through <= 1.8.9.
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 confidenceMissing Authorization vulnerability in the WC Pickup Store WordPress plugin allows unauthorized users to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to store management functionality.
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 WC Pickup Store plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and locate WC Pickup Store. Note the installed version number from the plugin version field.Affected if The plugin is installed and active, regardless of version, as no specific patched version range was provided.
-
Identify store management endpointsReview the plugin files (typically in wp-content/plugins/wc-pickup-store/) to identify PHP files handling store-related functionality. Look for files containing terms like 'store', 'location', 'pickup', or admin-related functions.Affected if The plugin exposes any store management functions that lack authorization checks.
-
Test for missing authorization on sensitive actionsUsing a low-privileged user account (e.g., subscriber) or unauthenticated request, attempt to access or modify store settings, add/edit/delete pickup locations, or access admin-area store functions that should require administrator privileges.Affected if Unprivileged users can access or modify store management functionality without proper capability checks.
-
Inspect plugin code for capability checksSearch plugin PHP files for WordPress capability checks such as 'current_user_can', 'manage_woocommerce', or 'administrator' before executing store management functions. Review AJAX handlers and form processing code.Affected if No capability checks exist before sensitive store operations, or checks are incorrectly implemented/missing.
-
Check WordPress roles and capabilities configurationNavigate to WordPress Users > Roles and Permissions panel if available, or use a role editor plugin to examine what capabilities are assigned to non-admin roles.Affected if Non-administrator roles have been granted elevated store management capabilities that should be restricted.
A user is affected if the WC Pickup Store plugin is active and allows unauthorized access to store management functions due to missing or inadequate capability checks on sensitive endpoints.
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 role-based access control (RBAC) checks and authorization validation on all sensitive endpoints within the plugin to verify user permissions before allowing access to store functions.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47634 — 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-2025-47634 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