CVE-2024-1954

Oliver POS – A WooCommerce Point of Sale (POS) <= 2.4.1.8 - Cross-Site Request Forgery

2024-02-27 00:00
Francesco Carlucci

Strategic Overview

Status
Patched in 2.4.1.9
Affected Version
<= 2.4.1.8
CVSS
6.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-1954
View all Oliver POS – WooCommerce POS for iPhone, iPad & Android vulnerabilities

At a glance

CVE-2024-1954 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Oliver POS WordPress plugin, affecting versions <= 2.4.1.8. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.4.1.9; sites on affected versions should update now. Disclosed February 2024, reported by Francesco Carlucci.

Vulnerability Overview

The Oliver POS – A WooCommerce Point of Sale (POS) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.4.1.8. This is due to missing or incorrect nonce validation in the includes/class-pos-bridge-install.php file. This makes it possible for unauthenticated attackers to perform several unauthorized actions like deactivating the plugin, disconnecting the subscription, syncing the status and more via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Oliver POS <= 2.4.1.8 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Oliver POS the fix is 2.4.1.9: builds <= 2.4.1.8 are affected, anything from 2.4.1.9 onward is not.

Remediation

Update to version 2.4.1.9, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Oliver POS: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Oliver POS 2.4.1.9 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C