CVE-2024-56061

Computer Repair Shop <= 3.8119 - Authenticated (Customer+) Privilege Esclation via Account Takeover

2024-12-18 00:00
SOPROBRO

Strategic Overview

Status
Patched in 3.8120
Affected Version
<= 3.8119
CVSS
9.8Critical
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-56061
View all RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress vulnerabilities

At a glance

CVE-2024-56061 is a critical-severity Missing Authorization vulnerability in the RepairBuddy WordPress plugin, affecting versions <= 3.8119. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.8120; sites on affected versions should update now. Disclosed December 2024, reported by SOPROBRO.

Vulnerability Overview

The CRM WordPress Plugin – RepairBuddy plugin for WordPress is vulnerable to account takeover in all versions up to, and including, 3.8119. This makes it possible for authenticated attackers, with Customer-level access and above, to gain access to other users accounts which may have higher privileges.

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, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in RepairBuddy <= 3.8119 takes an account at Customer level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For RepairBuddy the fix is 3.8120: builds <= 3.8119 are affected, anything from 3.8120 onward is not.

Remediation

Update to version 3.8120, 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: RepairBuddy 3.8120 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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