CVE-2026-39662
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 ProWCPlugins Product Price by Formula for WooCommerce product-price-by-formula-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Product Price by Formula for WooCommerce: from n/a through <= 2.5.6.
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 confidenceA missing authorization vulnerability in the Product Price by Formula for WooCommerce plugin (versions up to 2.5.6) allows unauthenticated or unauthorized users to access functionality they should not have access to, likely enabling manipulation of product price formulas without proper capability checks.
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 the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Product Price by Formula for WooCommerce'. Note the installed version displayed next to the plugin name.Affected if The plugin is installed and the version is below 2.5.7 or cannot be determined
-
Identify the installed version numberLocate the plugin version in the plugin header comment within the main plugin file (typically in /wp-content/plugins/product-price-by-formula-for-woocommerce/ or similar path). Compare this version to 2.5.7 as the patched reference.Affected if The installed version is lower than 2.5.7 or the version cannot be verified
-
Inspect AJAX endpoints for missing capability checksReview the plugin PHP files for AJAX action handlers (add_action calls with wp_ajax_ or wp_ajax_nopriv_ prefixes). Check if these handlers include current_user_can() or similar capability verification before executing sensitive operations on pricing formulas.Affected if AJAX endpoints exist that process pricing formula data without verifying user capabilities (no current_user_can() check found)
-
Review callback functions for authorizationExamine the plugin PHP files for callback functions that handle product price modifications. Look for whether these functions first validate user permissions using current_user_can('manage_options') or 'edit_products' capability before allowing changes.Affected if Functions that modify pricing formulas do not perform capability checks at the function entry point
The environment is affected if the Product Price by Formula for WooCommerce plugin is installed with a version below 2.5.7 AND AJAX endpoints or functions lack proper capability validation before allowing access to pricing formula modifications.
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 the latest version when available. If no patch exists, implement proper WordPress capability checks (e.g., 'manage_options' or 'edit_products') on all AJAX endpoints and admin pages that handle price formula configuration.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39662 — 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-2026-39662 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