CVE-2026-39584
Description
RepairBuddy plugin ≤4.1132 has a broken access control vulnerability allowing subscribers to execute privileged actions.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
RepairBuddy plugin ≤4.1132 has a broken access control vulnerability allowing subscribers to execute privileged actions.
Vulnerability
A broken access control vulnerability exists in the RepairBuddy plugin for WordPress (plugin slug computer-repair-shop), affecting all versions up to and including 4.1132. The issue stems from missing authorization or authentication checks in a function, enabling subscribers to perform actions that should require higher privileges [1].
Exploitation
An authenticated attacker with subscriber-level access can exploit this vulnerability by sending crafted requests to the affected plugin endpoint. No specific network position or additional user interaction is required beyond standard WordPress authentication. The vulnerability is expected to be used in mass-exploit campaigns targeting thousands of websites [1].
Impact
Successful exploitation allows an unprivileged subscriber to execute a certain higher privileged action, leading to unauthorized modifications or data exposure. The CVSS v3 base score is 6.5 (Medium), indicating a moderate severity with potential for unauthorized access control bypass [1].
Mitigation
The vulnerability is fixed in version 4.1133 of the plugin. Users should update to this version or later immediately. As a workaround, Patchstack provides a mitigation rule to block attacks until the update is applied. For sites unable to update immediately, contacting the hosting provider or web developer is recommended [1].
AI Insight generated on Jun 15, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1- Range: <=4.1132
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
0No linked articles in our index yet.