dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-12617

MEDIUM · 5.4 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 →
60/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 WC Price History for Omnibus plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on several AJAX actions in all versions up to, and including, 2.1.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view and modify history 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 WC Price History for Omnibus WordPress plugin fails to enforce proper capability checks on multiple AJAX action handlers. This allows any authenticated user with Subscriber-level permissions (the lowest privilege level in WordPress) to execute these AJAX functions and access or manipulate price history data that should be restricted to higher-privileged roles like Administrators.

MitigationUpdate the plugin to the latest version which implements proper capability checks on AJAX actions. Until then, consider disabling the plugin or restricting user registration.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 the plugin is installed
    Navigate to WordPress Admin > Plugins and confirm 'WC Price History for Omnibus' is installed and active, or inspect the file wp-content/plugins/wc-price-history-for-omnibus/plugin.php to read the version header
    Affected if The plugin is installed and active
  2. Identify the installed version
    Open the plugin's main file (typically wc-price-history-for-omnibus.php or plugin.php in the plugin directory) and locate the Version header in the plugin comment block, then compare against the version that includes the fix
    Affected if The installed version predates the patched version with proper capability checks
  3. Check for low-privilege user accounts
    In WordPress Admin, go to Users and review the list. Note any users with the Subscriber role, or check if user registration is enabled under Settings > General > Membership
    Affected if Any Subscriber-level accounts exist, or user registration is enabled allowing public registration
  4. Test AJAX access from low-privilege account
    Using a Subscriber-level account, attempt to access wp-admin/admin-ajax.php with action parameters used by this plugin (such as wph_ajax requests). Send a authenticated request and observe if data is returned without permission errors
    Affected if AJAX requests execute successfully and return price history data despite the user lacking administrator privileges
  5. Review user role capabilities for AJAX actions
    Inspect the plugin source code in wp-content/plugins/wc-price-history-for-omnibus/ for AJAX callback functions and verify if they include current_user_can() or capability checks before processing requests
    Affected if AJAX handlers lack capability checks (no current_user_can() calls) and execute for any authenticated user

You are affected if the WC Price History for Omnibus plugin is installed with a vulnerable version AND any Subscriber-level user account exists or user registration is enabled, allowing low-privilege users to access restricted price history data via AJAX.

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 the latest version which implements proper capability checks on AJAX actions. Until then, consider disabling the plugin or restricting user registration.

Recommended fix Moderate confidence

2.1.4 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WC Price History for Omnibus' in the plugin list
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org/plugins/wc-price-history-for-omnibus and upload it
  5. After updating, verify the new version number reflects the patch (2.1.4 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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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