CVE-2026-76124: BuddyBoss App (WordPress plugin) · Unrestricted File Upload
Affects BuddyBoss App (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 3 Nov 2026, 12:58 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 8.8 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BuddyBossBuddyBoss App | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict subscriber-level user permissions where possible and monitor for suspicious file uploads. Avoid relying solely on client-supplied headers for file validation and implement server-side content inspection and extension validation as a mitigation.
Description
The BuddyBoss App plugin for WordPress up to version 3.2.1 contains an arbitrary file upload vulnerability via the send_feedback function. This flaw arises from insufficient server-side validation of uploaded file types, relying only on the client-supplied Content-Type header. Authenticated users with subscriber-level access or higher can upload potentially executable files, enabling remote code execution. Although uploaded files are intended to be deleted after email transmission, a race condition during SMTP execution allows access to these files, and files remain if wp_mail() fails.