CVE-2026-119514

RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress <= 4.1234 - Authenticated (Technician+) Privilege Escalation

2026-11-07 09:43
ZhugeZ

Strategic Overview

Status
Patched in 4.1235
Affected Plugin
RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress
Affected Version
<= 4.1234
CVSS
6.3Medium
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2026-119514
View all RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress vulnerabilities

At a glance

CVE-2026-119514 is a medium-severity Improper Privilege Management vulnerability in the RepairBuddy WordPress plugin, affecting versions <= 4.1234. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Technician level or above. The issue is fixed in version 4.1235; sites on affected versions should update now. Disclosed November 2026, reported by ZhugeZ.

Vulnerability Overview

The RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.1234. This is due to insufficient restriction on the capabilities a user may grant themselves. This makes it possible for authenticated attackers, with technician-level access and above, to elevate their privileges beyond those intended for their role.

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 interaction from a victim user.

CWE-269: Improper Privilege Management

Reaching this weakness in RepairBuddy <= 4.1234 takes an account at Technician level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For RepairBuddy the fix is 4.1235: builds <= 4.1234 are affected, anything from 4.1235 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-119514https://www.wordfence.com/threat-intel/vulnerabilities/id/a0caefd6-b54f-4318-81e2-0b71f2cf5019https://nvd.nist.gov/vuln/detail/CVE-2026-119514

Related records

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