What happened
BuddyBoss is a suite of WordPress plugins used to run community sites, membership portals and online courses. A critical flaw was found in the Social Login module of the BuddyBoss Addons plugin, specifically in sign-in with Apple and Facebook accounts. The vulnerability is tracked as CVE-2026-80188 and was published in the NVD database on November 20, 2026.
The vendor fixed the issue in BuddyBoss Addons 1.2.2. Its changelog for that release briefly says it fixed a security issue affecting social login. The changelog does not give a release date.
There is no confirmation yet that attackers are exploiting the flaw. It is not listed in the CISA KEV catalog, and ENISA’s European Vulnerability Database (record EUVD-2026-131560) does not report exploitation either. With critical WordPress plugin bugs, though, the gap between disclosure and the first attacks is often short, so don’t put off the update.
Why it is dangerous
This is an authentication bypass (CWE-287), a flaw in how the site checks who is logging in. According to the NVD description, during Apple or Facebook sign-in the plugin trusts the data inside the identity token without verifying that Apple or Facebook actually issued it. It then uses the email address in the token to link a foreign identity to an existing account on the site.
Picture a receptionist who lets you into the CEO’s office because you show a note with the CEO’s name on it, without ever checking who wrote the note. The attacker only needs the victim’s email address. No password, no account on the site, the attack works over the internet and the victim doesn’t have to click anything. The attacker links their identity to someone else’s account, administrators included, and then logs in as that person.
With a WordPress administrator account, an attacker effectively controls the whole site. They can read member data, change content and add users. WordPress administrators can usually install plugins as well, so an attacker could also run their own code on the server. On sites that also use the separate BuddyBoss App JWT component, NVD notes that the vulnerable request can return an application token immediately.
The CVSS score of 9.8 out of 10 (CVSS 3.1) was assigned by Wordfence, a company focused on WordPress security. CVSS is an international severity scale, and 9.8 means critical: attack over the network, no login, no user interaction, and high impact on confidentiality, integrity and availability. An EPSS score, which estimates the likelihood of exploitation, is not yet available for this flaw.
Who is affected
The vulnerable component is the BuddyBoss Addons plugin for WordPress, versions up to and including 1.2.1. According to NVD, exploitation requires all of the following:
- the BuddyBoss Platform plugin is installed and active
- the Social Login module is enabled
- Apple or Facebook sign-in is enabled and configured
Typical setups are community and membership sites, e-learning portals, company intranets built on WordPress and sites paired with the BuddyBoss App mobile app. If you don’t use BuddyBoss Addons, or don’t have Apple or Facebook sign-in turned on, this particular flaw doesn’t directly affect you. Updating is still worthwhile, since settings can change later.
How to check if you are affected
You can find the version in the WordPress admin under Plugins, where BuddyBoss Addons shows its version number. If WP-CLI is available on the server, run this command from the site directory. It only lists plugins and changes nothing:
wp plugin list --fields=name,status,version | grep -i buddyboss
Without WP-CLI, you can read the version straight from the plugin’s main file. The directory path may differ on your server:
grep -i -m1 'Version:' wp-content/plugins/buddyboss-addons/buddyboss-addons.php
If the version is 1.2.1 or lower and the BuddyBoss Platform plugin is active, check the BuddyBoss settings to see whether the Social Login module and Apple or Facebook sign-in are enabled. If they are, the site is vulnerable.
How to fix it
The vendor fixed the flaw in BuddyBoss Addons 1.2.2. The vendor’s changelog already lists newer releases, the latest being 1.3.4, so update straight to the newest version available to you. Here’s the order to follow:
- Back up the site’s database and files.
- Update BuddyBoss Addons from the Plugins screen in the WordPress admin. If automatic updates aren’t available, download the new package following the vendor’s instructions.
- Confirm the version now shows 1.2.2 or later.
- Test that Apple and Facebook sign-in still work.
- Go through the checks in the compromise section below, especially the list of administrators.
The vendor has not published a workaround. Since NVD says exploitation requires the Social Login module with Apple or Facebook enabled, a sensible stopgap if you can’t update right away is to turn off that module or those providers until you do. Users who have a password set can log in the usual way in the meantime.
The flaw is not in the CISA KEV catalog, so CISA has not set a mandatory remediation deadline. With a score of 9.8, though, we recommend updating as soon as possible, ideally today.
What if you may already be compromised
Neither the vendor nor NVD lists specific indicators of compromise yet. If you ran a vulnerable version with Apple or Facebook sign-in enabled, check in particular:
- the list of administrators and other high-privilege accounts for anyone you don’t recognize
- whether admin accounts have Apple or Facebook identities linked that you don’t know about, if the interface shows this
- new or modified plugins, themes and PHP files
- web server logs, especially unusual REST API requests and admin logins from unfamiliar IP addresses
The first command lists the site’s administrators, the second finds PHP files changed in the last 30 days. Both are read-only. After updating the plugin, its new files will show up in the list too, which is expected:
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered
find wp-content -name '*.php' -mtime -30
If anything looks off, change admin passwords, unlink unknown social identities and rotate the security keys in wp-config.php, which logs out every session. If you use BuddyBoss App, ask the vendor how to revoke issued application tokens. If you find an unknown administrator, foreign code on the server or suspect member data was exposed, bring in a specialist and consider your GDPR breach notification duties.