CVE-2024-1954 MEDIUM

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

Vendor Oliverpos
Product Oliver POS – A WooCommerce Point of Sale (POS)
Weakness CWE-352 · CSRF
Published February 28, 2024
Last update April 8, 2026

CVSS base score

6.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Oliver POS for WooCommerce contains a cross-site request forgery (CSRF) vulnerability affecting versions up to 2.4.1.8. An attacker can craft a malicious link or page that, when visited by a logged-in site administrator, performs unwanted actions on the POS system without the admin's knowledge or consent. The vulnerability requires user interaction and affects confidentiality, integrity, and availability of the POS data.

What an attacker can do

03Attacker Capabilities

Trick a logged-in admin into performing unwanted POS actions by visiting a malicious link or page.

Potential impact on your site

04Site Impact

An attacker can modify POS settings, create fraudulent transactions, or disrupt sales operations if an admin visits a compromised page.

Conditions required to exploit

05Prerequisites

Admin must be logged in and visit attacker-controlled page or click a malicious link.

Key dates

06Disclosure timeline

February 28, 2024 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE