CVE-2025-64285
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 Premmerce Premmerce Wholesale Pricing for WooCommerce premmerce-woocommerce-wholesale-pricing allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Premmerce Wholesale Pricing for WooCommerce: from n/a through <= 1.1.10.
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 Premmerce Wholesale Pricing for WooCommerce plugin. The vulnerability allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to wholesale pricing functionality or data that should be restricted to privileged users.
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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify if Premmerce Wholesale Pricing for WooCommerce is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Premmerce Wholesale Pricing for WooCommerce' or check the plugin files in wp-content/plugins/ for the premmerce-wholesale-pricing directoryAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin Plugins list, click on the plugin to view details and note the version number, or read the main plugin PHP file header for the 'Version' tagAffected if The installed version is any version of this plugin (since no fixed version is specified)
-
Verify admin interface access controlsNavigate to WooCommerce > Wholesale Pricing settings. Check if the plugin allows access to wholesale pricing configuration without proper capability checks. Test accessing admin pages as a non-administrator user roleAffected if Non-privileged users (e.g., shop managers, editors, subscribers) can access or modify wholesale pricing settings
-
Test AJAX and action endpoint authorizationUse browser developer tools to identify AJAX endpoints (typically under wp-admin/admin-ajax.php?action=premmerce_*) or form actions. Attempt to access or execute these as an unauthenticated or low-privileged userAffected if AJAX/action endpoints respond successfully without proper capability verification or nonce validation
If the Premmerce Wholesale Pricing for WooCommerce plugin is installed and accessible to users without administrator privileges, the environment is likely affected by this missing authorization vulnerability.
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 dataApply the latest available patch or update from the vendor. If no patch exists, restrict access to the affected plugin's admin interfaces and verify all AJAX/action endpoints have proper capability checks and nonce validations.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64285 — 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-64285 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