CVE-2026-0820

RepairBuddy <= 4.1116 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary Signature Upload to Orders

2026-01-16 14:36
Teerachai Somprasong

Strategic Overview

Status
Patched in 4.1121
Affected Plugin
RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress
Affected Version
<= 4.1116
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-0820
View all RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress vulnerabilities

At a glance

CVE-2026-0820 is a medium-severity Missing Authorization vulnerability in the RepairBuddy WordPress plugin, affecting versions <= 4.1116. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.1121; sites on affected versions should update now. Disclosed January 2026, reported by Teerachai Somprasong.

Vulnerability Overview

The RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference due to missing capability checks on the wc_upload_and_save_signature_handler function in all versions up to, and including, 4.1116. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary signatures to any order in the system, potentially modifying order metadata and triggering unauthorized status changes.

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-862: Missing Authorization

Reaching this weakness in RepairBuddy <= 4.1116 takes an account at Subscriber 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 4.1121: builds <= 4.1116 are affected, anything from 4.1121 onward is not.

Remediation

Update to version 4.1121, 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.1121 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-0820https://www.wordfence.com/threat-intel/vulnerabilities/id/1b2ad299-03b1-4b9e-a241-d2ad2d85c3achttps://nvd.nist.gov/vuln/detail/CVE-2026-0820

Related records

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