dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3567

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 4.1132. The plugin exposes two AJAX handlers that, when combined, allow any authenticated user to modify admin-level plugin settings. First, the wc_rb_get_fresh_nonce() function (registered via wp_ajax and wp_ajax_nopriv hooks) allows any user to generate a valid WordPress nonce for any arbitrary action name by simply providing the nonce_name parameter, with no capability checks. Second, the wc_rep_shop_settings_submission() function only verifies the nonce (wcrb_main_setting_nonce) but performs no current_user_can() capability check before updating 15+ plugin options via update_option(). This makes it possible for authenticated attackers, with subscriber-level access and above, to modify all plugin configuration settings including business name, email, logo, menu label, GDPR settings, and more by first minting a valid nonce via the wc_rb_get_fresh_nonce endpoint and then calling the settings submission handler.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The RepairBuddy WordPress plugin exposes two AJAX endpoints that together allow privilege escalation. The wc_rb_get_fresh_nonce() function (accessible to unauthenticated users via wp_ajax_nopriv) generates valid WordPress nonces for any action without capability checks. The wc_rep_shop_settings_submission() function then accepts this nonce but lacks current_user_can() validation, allowing any authenticated user (subscriber+) to modify 15+ plugin settings including business name, email, logo, and GDPR configuration.

MitigationAdd capability checks (e.g., current_user_can('manage_options')) to wc_rep_shop_settings_submission() before processing update_option() calls, and restrict wc_rb_get_fresh_nonce() to authenticated users with appropriate privileges or remove the wp_ajax_nopriv hook registration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify RepairBuddy plugin is installed
    Check the WordPress plugins directory or use WP-CLI: wp plugin list --search='repairbuddy' or inspect /wp-content/plugins/ for a repairbuddy folder
    Affected if The RepairBuddy plugin is present in the WordPress installation
  2. Check if AJAX endpoint wc_rb_get_fresh_nonce is registered for unauthenticated access
    Search plugin source code for 'wp_ajax_nopriv_wc_rb_get_fresh_nonce' or inspect the plugin's main PHP file for add_action('wp_ajax_nopriv_wc_rb_get_fresh_nonce', ...)
    Affected if The wp_ajax_nopriv hook is registered for wc_rb_get_fresh_nonce, allowing unauthenticated nonce generation
  3. Inspect wc_rep_shop_settings_submission for capability checks
    Locate the wc_rep_shop_settings_submission function in the plugin code and search for 'current_user_can' or 'manage_options' within that function
    Affected if No current_user_can() check is performed before processing settings updates
  4. Check for exposed plugin settings that can be modified
    Identify if the plugin handles update_option calls for settings like business name, email, logo, or GDPR options - look for the settings array or form submission handlers
    Affected if The plugin processes update_option calls without verifying user capabilities
  5. Confirm user role access
    Review if any authenticated user with subscriber-level access can trigger the settings update endpoint - check the AJAX action registration for wc_rep_shop_settings_submission
    Affected if The settings submission endpoint is accessible to subscriber-level users or below without proper authorization

The environment is affected if the RepairBuddy plugin is installed AND the wc_rb_get_fresh_nonce AJAX endpoint is hooked to wp_ajax_nopriv AND the wc_rep_shop_settings_submission function lacks current_user_can() validation before processing settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add capability checks (e.g., current_user_can('manage_options')) to wc_rep_shop_settings_submission() before processing update_option() calls, and restrict wc_rb_get_fresh_nonce() to authenticated users with appropriate privileges or remove the wp_ajax_nopriv hook registration.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3567 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3567 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data