dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-12266

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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 ELEX WooCommerce Dynamic Pricing and Discounts plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the elex_dp_export_rules() and elex_dp_import_rules() functions in all versions up to, and including, 2.1.7. This makes it possible for unauthenticated attackers to import and export product rules along with obtaining phpinfo() data

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 ELEX WooCommerce Dynamic Pricing and Discounts plugin lacks authorization checks on elex_dp_export_rules() and elex_dp_import_rules() functions, allowing unauthenticated users to export/import product pricing rules and retrieve phpinfo() data. This is a Broken Access Control vulnerability (CWE-862) where WordPress capability checks are missing before executing sensitive operations.

MitigationUpdate the plugin to version 2.1.8 or later which adds proper capability checks. Until patched, consider disabling the plugin or implementing WAF rules to block access to the vulnerable endpoints.

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

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

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

  1. Verify ELEX WooCommerce Dynamic Pricing plugin is installed
    Locate the plugin directory in WordPress wp-content/plugins/ folder, typically named 'elex-woocommerce-dynamic-pricing-and-discounts' or similar ELEX pricing plugin folder
    Affected if The plugin directory exists in the WordPress plugins folder
  2. Check installed plugin version
    Read the main plugin file (usually plugin root目录下的主文件) or check WordPress plugin administration panel to find the installed version number
    Affected if Version is lower than 2.1.8 (vulnerable versions)
  3. Confirm WooCommerce is active
    Verify WooCommerce plugin is installed and active in WordPress admin panel, as this is a WooCommerce-dependent plugin
    Affected if WooCommerce is active alongside a vulnerable version of the ELEX pricing plugin
  4. Identify vulnerable function exposure
    Inspect plugin source code for elex_dp_export_rules() and elex_dp_import_rules() functions - check if these functions are hooked to AJAX or public endpoints without capability checks (look for 'add_action' calls without 'manage_woocommerce' or 'manage_options' capability verification)
    Affected if Functions exist and are exposed without admin capability checks (no current_user_can() validation before execution)
  5. Test for unauthenticated access
    If accessible, send a crafted request to common AJAX endpoints (admin-ajax.php?action=elex_dp_export_rules or similar) without authentication cookies - check if the server responds with pricing data or phpinfo() output
    Affected if Unauthenticated requests return pricing rules data or phpinfo() output

User is affected if ELEX WooCommerce Dynamic Pricing and Discounts plugin version is below 2.1.8, WooCommerce is active, and the vulnerable export/import functions are accessible without authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 2.1.8 or later which adds proper capability checks. Until patched, consider disabling the plugin or implementing WAF rules to block access to the vulnerable endpoints.

Recommended fix Moderate confidence

Version 2.1.8 or latest available version of the ELEX WooCommerce Dynamic Pricing and Discounts plugin

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'ELEX WooCommerce Dynamic Pricing and Discounts' in the plugin list
  4. 4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org/plugins/elex-woocommerce-dynamic-pricing-and-discounts
  5. 5. After updating, verify the new version is at least 2.1.8 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12266 — 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-12266 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