RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress
computer-repair-shop · plugin
Known security vulnerabilities for RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress. Find out in seconds which version runs on your site with WP Lens.
11 known vulnerabilities
1 critical · 3 exploitable without logging in · 1 with public exploit code · latest Sep 10, 2026
Listed on wordpress.org · latest 4.1231 · last updated Oct 1, 2026 · 400+ installs
wordpress.org status checked on Oct 5, 2026
Vulnerabilities
- Critical 9.8
CVE-2024-51793unauthenticated≤ 3.8115
WordPress RepairBuddy plugin <= 3.8115 - Arbitrary File Upload vulnerability
- High 8.8
CVE-2024-56061login required≤ 3.8119
WordPress RepairBuddy plugin <= 3.8119 - Account Takeover vulnerability
- High 8.8
CVE-2024-12259subscriber+≤ 3.8120
CRM WordPress Plugin – RepairBuddy <= 3.8120 - Missing Authorization to Account Takeover/Privilege Escalation
- High 7.5
CVE-2026-81803subscriber+≤ 4.1224
WordPress RepairBuddy plugin <= 4.1224 - Remote Code Execution (RCE) vulnerability
- Medium 6.5
CVE-2026-39584subscriber+≤ 4.1132
WordPress RepairBuddy plugin <= 4.1132 - Broken Access Control vulnerability
- Medium 5.3
CVE-2026-78291unauthenticated≤ 4.1223
WordPress RepairBuddy plugin <= 4.1223 - Broken Access Control vulnerability
- Medium 5.3
CVE-2026-39586unauthenticated≤ 4.1132
WordPress RepairBuddy plugin <= 4.1132 - Sensitive Data Exposure vulnerability
- Medium 5.3
CVE-2026-3567subscriber+≤ 4.1132
RepairBuddy <= 4.1132 - Missing Authorization to Authenticated (Subscriber+) Plugin Settings Modification via wc_rep_shop_settings_submission AJAX Action
- Medium 4.3
CVE-2026-24638login required≤ 4.1121
WordPress RepairBuddy plugin <= 4.1121 - Broken Access Control vulnerability
- Medium 4.3
CVE-2026-0820subscriber+≤ 4.1116
RepairBuddy <= 4.1116 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary Signature Upload to Orders
- Medium 4.3
CVE-2025-32277login required≤ 3.8213
WordPress RepairBuddy plugin <= 3.8213 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).