dbcve.org
License Manager For WoocommerceWordPress extension · Wpexperts

CVE-2024-1639

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-21
Fix available
A fix is available. Upgrade to after 3.0.7 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The License Manager for WooCommerce plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the showLicenseKey() and showAllLicenseKeys() functions in all versions up to, and including, 3.0.6. This makes it possible for authenticated attackers, with admin dashboard access (contributors by default due to WooCommerce) to view arbitrary decrypted license keys. The functions contain a referrer nonce check. However, these can be retrieved via the dashboard through the "license" JS variable. Please note that the version in trunk is patched, however, the 3.0.7 tagged version is not.

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 · high confidence

The License Manager for WooCommerce plugin lacks proper capability checks on showLicenseKey() and showAllLicenseKeys() functions, allowing any authenticated user with contributor-level access to view decrypted license keys. While nonce checks exist, license keys are exposed through the dashboard's JavaScript variables, enabling direct retrieval.

MitigationUpdate to the patched version in trunk (or wait for a properly patched release beyond 3.0.7). Restrict admin dashboard access to trusted users until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
License Manager For WoocommerceWordPress extension
Affected:<= 3.0.7

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed and active
    Navigate to WordPress admin > Plugins and look for 'License Manager for WooCommerce' by Wpexperts, or check the plugin files in wp-content/plugins/
    Affected if The plugin is installed and active with version 3.0.7 or lower
  2. Check the installed plugin version
    In WordPress admin > Plugins, find the plugin and verify the version number displayed, or read the main plugin PHP file header
    Affected if Version is 3.0.7 or any version 'less than or equal to' 3.0.7
  3. Identify users with contributor-level access or higher
    Go to WordPress admin > Users and review the role column for each user; contributor role is sufficient to exploit this flaw
    Affected if Any authenticated user exists with contributor role or above who is not an administrator with full privileges
  4. Inspect JavaScript variables in the dashboard for exposed license keys
    View the page source of the WordPress admin dashboard while logged in as a contributor user, then search for license-related strings (such as 'licenseKey', 'license_key', or similar decrypted key values) in the JavaScript
    Affected if Decrypted license keys appear in JavaScript variables accessible to contributor-level users

You are affected if the plugin version is 3.0.7 or lower and any contributor-level or higher authenticated user exists in your WordPress installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.0.7
Interim mitigation

Update to the patched version in trunk (or wait for a properly patched release beyond 3.0.7). Restrict admin dashboard access to trusted users until patched.

Recommended fix High confidence

Latest version of License Manager for WooCommerce (newer than 3.0.7)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find 'License Manager for WooCommerce'
  4. Check if an update is available and update to the latest version
  5. If no update is visible in WordPress, manually download the latest version from the WordPress plugin repository and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in License Manager For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1639 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1639 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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