CVE-2026-81803

RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress <= 4.1224 - Authenticated (Subscriber+) Remote Code Execution

2026-09-09 00:00
Nasur ullah

Strategic Overview

Status
Patched in 4.1225
Affected Plugin
RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress
Affected Version
<= 4.1224
CVSS
8.8High
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2026-81803
View all RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress vulnerabilities

At a glance

CVE-2026-81803 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the RepairBuddy WordPress plugin, affecting versions <= 4.1224. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.1225; sites on affected versions should update now. Disclosed September 2026, reported by Nasur ullah.

Vulnerability Overview

The RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.1224. This is due to insufficient validation of user supplied input before it is executed. This makes it possible for authenticated attackers, with subscriber-level access and above, to execute arbitrary code on the server.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in RepairBuddy <= 4.1224 takes an account at Subscriber level or above. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For RepairBuddy the fix is 4.1225: builds <= 4.1224 are affected, anything from 4.1225 onward is not.

Remediation

Update to version 4.1225, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: RepairBuddy 4.1225 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-81803https://www.wordfence.com/threat-intel/vulnerabilities/id/bfb07058-3781-4456-8595-2edf92ef391ahttps://nvd.nist.gov/vuln/detail/CVE-2026-81803

Related records

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