dbcve.org
Oliver PosWordPress extension · Oliverpos

CVE-2024-0702

HIGH · 7.3 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 2.4.2.1 or later.
See remediation →
82/100
Remediation priority · High
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 Oliver POS – A WooCommerce Point of Sale (POS) plugin for WordPress is vulnerable to unauthorized access due to missing capability checks on several functions hooked via AJAX in the includes/class-pos-bridge-install.php file in all versions up to, and including, 2.4.2.1 This makes it possible for authenticated attackers, with subscriber-level access and above, to perform several unauthorized actions like deactivating the plugin, disconnecting the subscription, syncing the status and more.

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 Oliver POS WordPress plugin versions up to 2.4.2.1 lacks capability checks on AJAX functions in includes/class-pos-bridge-install.php. Authenticated users with subscriber-level permissions (the lowest privilege role) can invoke these unprotected AJAX endpoints to perform administrative actions including plugin deactivation, subscription disconnection, and status synchronization.

MitigationAdd WordPress capability checks (e.g., current_user_can('manage_options')) to all AJAX handlers in the affected file and implement proper nonces to prevent CSRF attacks.

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
Oliver PosWordPress extension
Affected:< 2.4.2.1

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
Low

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

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

  1. Confirm Oliver POS plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Oliver POS' or check the wp-content/plugins directory for an 'oliver-pos' folder
    Affected if The plugin is present in the WordPress installation
  2. Check the installed Oliver POS version
    In WordPress admin, go to Plugins > Installed Plugins, find Oliver POS, and view the version number displayed below the plugin name
    Affected if The installed version is less than 2.4.2.1 (any version up to and including 2.4.2.1 is affected)
  3. Verify the vulnerable file exists
    Check if the file wp-content/plugins/oliver-pos/includes/class-pos-bridge-install.php exists on the server
    Affected if The file exists and the plugin version is below 2.4.2.1
  4. Inspect AJAX function registrations in the vulnerable file
    Examine class-pos-bridge-install.php for add_action('wp_ajax_', ...) calls and check if they include current_user_can() capability checks or nonce verification
    Affected if AJAX handlers do not contain capability checks (such as current_user_can('manage_options')) before performing actions
  5. Check for subscriber-level user accounts
    In WordPress admin, go to Users and review if any users have the Subscriber role assigned
    Affected if Any subscriber-level users exist in the WordPress installation

A user is affected if Oliver POS plugin version is 2.4.2.1 or lower, the vulnerable AJAX file exists without capability checks, and any subscriber-level users are present in WordPress.

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 2.4.2.1 or later
Fixed in 2.4.2.1
Interim mitigation

Add WordPress capability checks (e.g., current_user_can('manage_options')) to all AJAX handlers in the affected file and implement proper nonces to prevent CSRF attacks.

Recommended fix High confidence

2.4.2.2 or latest available version

  1. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  2. Locate 'Oliver POS – A WooCommerce Point of Sale' plugin
  3. Click 'Update now' if an update is available, or manually upload version 2.4.2.2 or later from the WordPress plugin repository
  4. After updating, verify the plugin is functioning correctly by testing POS operations
  5. Confirm the update completed successfully via Plugins list

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

Fix this in Oliver Pos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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