The BuddyBoss App plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including
Source GCVE Database
Not known to be exploited · CVSS 8.8 High.
Data as of 3 Nov 2026, 16:42 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 capabilities where possible and monitor for suspicious file uploads. Consider disabling or limiting the use of the send_feedback function if feasible. Follow vendor guidance once available.
Description
The BuddyBoss App plugin for WordPress contains an arbitrary file upload vulnerability in all versions up to and including 3.2.1. This flaw arises from insufficient server-side validation of uploaded files, relying only on the client-supplied Content-Type header. Authenticated users with subscriber-level access or higher can exploit this to upload potentially executable files, enabling remote code execution. Uploaded files are typically deleted after email transmission, but a race condition during SMTP execution allows access to these files. Additionally, files persist indefinitely if the wp_mail() function fails.