Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-0820: CWE-862 Missing Authorization in sweetdaisy86 RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress

0
Medium
VulnerabilityCVE-2026-0820cvecve-2026-0820cwe-862
Published: Sat Jan 17 2026 (01/17/2026, 03:24:23 UTC)
Source: CVE Database V5
Vendor/Project: sweetdaisy86
Product: RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress

Description

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.

AI-Powered Analysis

AILast updated: 01/24/2026, 19:50:37 UTC

Technical Analysis

CVE-2026-0820 is a vulnerability classified under CWE-862 (Missing Authorization) found in the RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress, a plugin designed to manage repair shop CRM and booking functionalities. The flaw exists in the wc_upload_and_save_signature_handler function, which lacks proper capability checks before allowing the upload and saving of signature files associated with orders. This missing authorization check enables any authenticated user with Subscriber-level access or higher to upload arbitrary signature files to any order within the system. Consequently, attackers can modify order metadata and trigger unauthorized status changes without requiring administrative privileges or user interaction. The vulnerability affects all versions up to and including 4.1116. The CVSS v3.1 base score is 5.3, indicating a medium severity with network attack vector, low attack complexity, no privileges required, and no user interaction needed. Although no public exploits are known, the vulnerability poses a risk of data integrity compromise and potential business process disruption. The lack of authorization checks in a function handling sensitive order data is a critical design oversight that could be exploited to manipulate orders, potentially leading to fraudulent activities or operational issues in repair shop environments using this plugin.

Potential Impact

For European organizations, especially small and medium-sized enterprises (SMEs) operating repair shops or service centers using WordPress with the RepairBuddy plugin, this vulnerability could lead to unauthorized modification of order data, including fraudulent status changes or tampering with digital signatures. This undermines the integrity of business transactions and customer trust. The impact includes potential financial losses due to fraudulent orders or service manipulations, disruption of order processing workflows, and reputational damage. Since the vulnerability requires only Subscriber-level access, it lowers the barrier for exploitation, increasing risk from insider threats or compromised low-privilege accounts. Additionally, regulatory compliance risks may arise if order data integrity is critical under GDPR or other data protection laws. The threat could also facilitate further attacks by manipulating order statuses to trigger unintended business logic or automated processes.

Mitigation Recommendations

1. Apply patches or updates from the plugin vendor as soon as they become available to address the missing authorization checks. 2. Until patches are released, restrict the assignment of Subscriber-level or higher roles to trusted users only, minimizing the risk of exploitation by unauthorized personnel. 3. Implement strict role-based access controls (RBAC) and review user permissions regularly to ensure minimal necessary privileges. 4. Monitor order metadata changes and signature uploads for unusual or unauthorized activity using WordPress audit logging plugins or SIEM integration. 5. Employ web application firewalls (WAF) with custom rules to detect and block suspicious requests targeting the vulnerable function. 6. Educate staff about the risks of account compromise and enforce strong authentication mechanisms, including multi-factor authentication (MFA) for all users with access to the WordPress backend. 7. Consider isolating critical business functions or sensitive plugins in segmented environments to limit lateral movement in case of compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-01-09T18:16:47.579Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 696b0749b22c7ad868788fdb

Added to database: 1/17/2026, 3:51:37 AM

Last enriched: 1/24/2026, 7:50:37 PM

Last updated: 2/7/2026, 3:52:48 AM

Views: 58

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats