CVE-2024-2472

LatePoint Plugin <= 4.9.9 - Missing Authorization and Sensitive Information Exposure via IDOR

2024-06-13 21:00
Gharib Sharifi

Strategic Overview

Status
Patched in 4.9.9.1
Affected Plugin
LatePoint Plugin
Affected Version
<= 4.9.9
CVSS
9.1Critical
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-2472
View all LatePoint Plugin vulnerabilities

At a glance

CVE-2024-2472 is a critical-severity Authorization Bypass Through User-Controlled Key vulnerability in the LatePoint Plugin WordPress plugin, affecting versions <= 4.9.9. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires no authentication. The issue is fixed in version 4.9.9.1; sites on affected versions should update now. Disclosed June 2024, reported by Gharib Sharifi.

Vulnerability Overview

The LatePoint Plugin plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to a missing capability check on the 'start_or_use_session_for_customer' function in all versions up to and including 4.9.9. This makes it possible for unauthenticated attackers to view other customer's cabinets, including the ability to view PII such as email addresses and to change their LatePoint user password, which may or may not be associated with a WordPress account.

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, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity.

CWE-639: Authorization Bypass Through User-Controlled Key

LatePoint Plugin <= 4.9.9 carries this weakness at start_or_use_session_for_customer, and reaching it takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For LatePoint Plugin the fix is 4.9.9.1: builds <= 4.9.9 are affected, anything from 4.9.9.1 onward is not.

Remediation

Update to version 4.9.9.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: LatePoint Plugin 4.9.9.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-2472https://www.wordfence.com/threat-intel/vulnerabilities/id/6215fa9f-06bc-4dc8-b1f5-a3bb75749f1dhttps://nvd.nist.gov/vuln/detail/CVE-2024-2472

Related records

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