Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-13513: CWE-862 Missing Authorization in oliverpos Oliver POS – A WooCommerce Point of Sale (POS)

0
Critical
VulnerabilityCVE-2024-13513cvecve-2024-13513cwe-862
Published: Sat Feb 15 2025 (02/15/2025, 07:33:40 UTC)
Source: CVE Database V5
Vendor/Project: oliverpos
Product: Oliver POS – A WooCommerce Point of Sale (POS)

Description

CVE-2024-13513 is a critical vulnerability in the Oliver POS WooCommerce Point of Sale plugin for WordPress, affecting all versions up to 2. 4. 2. 3. The flaw arises from missing authorization controls in the plugin's logging functionality, allowing unauthenticated attackers to access sensitive information such as the clientToken. This token can be leveraged to modify user account details, including emails and account types, and ultimately change passwords, leading to full site takeover. Although version 2. 4. 2. 3 disabled logging, existing log files remain exploitable.

AI-Powered Analysis

AILast updated: 02/25/2026, 23:56:26 UTC

Technical Analysis

CVE-2024-13513 is a critical missing authorization vulnerability (CWE-862) in the Oliver POS plugin for WooCommerce on WordPress, present in all versions up to and including 2.4.2.3. The vulnerability stems from the plugin's logging mechanism, which inadvertently exposes sensitive data such as the clientToken to unauthenticated attackers. This clientToken is a sensitive credential that enables attackers to manipulate user account information, including changing email addresses and account types. By exploiting this, attackers can reset user passwords and gain full administrative control over the WordPress site, effectively resulting in a complete site takeover. The vulnerability requires no authentication or user interaction and can be exploited remotely over the network. Although the vendor disabled logging in version 2.4.2.3, sites with pre-existing log files remain vulnerable unless those files are deleted or secured. The CVSS v3.1 base score of 9.8 reflects the high impact on confidentiality, integrity, and availability, combined with the ease of exploitation. No known public exploits have been reported yet, but the severity and nature of the flaw make it a critical risk for affected installations.

Potential Impact

The impact of CVE-2024-13513 is severe for organizations using the Oliver POS WooCommerce plugin. Exploitation allows attackers to bypass authentication controls and extract sensitive tokens, enabling them to alter user accounts and reset passwords. This leads to complete site takeover, which can result in data breaches, unauthorized transactions, loss of customer trust, and potential financial fraud. Since WooCommerce is widely used for e-commerce, compromised sites may face significant operational disruption, reputational damage, and regulatory consequences. The vulnerability also threatens the confidentiality of customer data and the integrity of sales and inventory records. Organizations that have not removed or secured legacy log files remain at risk even if they have updated to the latest plugin version. The ease of remote exploitation without credentials or user interaction increases the likelihood of automated attacks and widespread compromise.

Mitigation Recommendations

To mitigate CVE-2024-13513, organizations should immediately audit their WordPress sites using the Oliver POS plugin to identify and securely delete any existing log files that contain sensitive clientTokens. Updating the plugin to the latest version (post-2.4.2.3) is essential, as logging has been disabled to prevent further exposure. However, updating alone is insufficient without removing legacy logs. Implement strict file permissions on the WordPress installation to restrict access to sensitive files and directories. Employ web application firewalls (WAFs) to detect and block suspicious requests targeting the plugin endpoints. Monitor logs for unusual activity related to user account changes or password resets. Additionally, enforce multi-factor authentication (MFA) for administrative accounts to reduce the risk of account takeover. Regularly review and limit plugin usage to only trusted and actively maintained extensions. Finally, conduct security awareness training for administrators to recognize and respond to potential exploitation attempts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-01-17T16:13:09.022Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e5cb7ef31ef0b59ef12

Added to database: 2/25/2026, 9:49:16 PM

Last enriched: 2/25/2026, 11:56:26 PM

Last updated: 2/26/2026, 10:08:31 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats