On this page (7 sections)

A critical vulnerability, tracked as CVE-2026-80188, affects the BuddyBoss Addons plugin for WordPress in versions up to and including 1.2.1. According to the GitHub Advisory Database entry, an unauthenticated attacker who knows a user's email address can link their own social identity to that user's account and then sign in as them, including as an administrator.

If you run a community, membership or learning site built on BuddyBoss and you offer Apple or Facebook login, you should check your setup today. At the time of writing, only the advisory data (also mirrored by NVD) describes the issue, and the research available to us does not state whether it is being exploited.

What happened

The advisory was published on November 20, 2026 and describes an authentication bypass that leads to account takeover. The problem sits in the Social Login REST endpoint of the BuddyBoss Addons plugin. That endpoint accepts identity-token claims from Apple and Facebook without verifying them, then attaches an attacker-controlled provider identifier to an existing WordPress user chosen by the email claim in the token.

In practice, the attacker does not need a password, a session or any user interaction. Knowing a target's email address is enough, and the advisory says this includes administrator accounts.

Technical details in plain terms

Social login normally works like this: the user signs in at Apple or Facebook, the provider hands back a signed token describing who they are, and the website checks that signature before trusting anything inside it. This flaw is a failure at that checking step. The endpoint trusts claims that were never verified, so a forged token carrying a victim's email can be matched to the victim's WordPress account.

Once the attacker's provider identity is linked to the account, signing in through that provider logs them in as the victim. The advisory adds that on sites using the separate BuddyBoss App JWT component, the vulnerable REST request can return an application token immediately, which shortens the path to access.

This weakness class is CWE-287, Improper Authentication: the product does not prove, or insufficiently proves, that an identity claim is correct. We are deliberately not describing request formats or exploit steps.

Who is exposed

The advisory lists several conditions that must all be true for exploitation:

  • The BuddyBoss Addons plugin is installed at version 1.2.1 or earlier.
  • The BuddyBoss Platform plugin is installed and active.
  • The Social Login module is enabled.
  • The selected provider (Apple or Facebook) is enabled and configured.

If any of those is missing, the advisory says exploitation is not successful. Sites that use BuddyBoss but do not offer social login are therefore in a much better position, though updating is still sensible. Membership sites, online course sites and communities with privileged accounts are the most attractive targets, since an administrator takeover gives full control of the site.

How to check your exposure

First, find out whether the plugin is present and which version it runs. This WP-CLI command lists installed plugins with their status and version; look for the BuddyBoss Addons and BuddyBoss Platform entries and compare the version against 1.2.1.

List installed plugins, status and versions (run from the WordPress root)WP-CLI
wp plugin list --fields=name,status,version,update

Then confirm in the WordPress admin whether the Social Login module is switched on and whether Apple or Facebook is configured as a provider. You can also see known issues per plugin on our WordPress plugin vulnerability listing and read how to judge a plugin in Is my WordPress plugin vulnerable?.

What to do now

The advisory data we reviewed lists patched versions as unknown. The vendor reference URL points to a release note named "addons 1.2.2", but we could not confirm from the research what that release changes. Read the BuddyBoss release page yourself before relying on it.
  1. Identify whether BuddyBoss Addons 1.2.1 or earlier is installed on any of your sites.
  2. Check the vendor's release page and update the plugin to the newest version it offers, testing on staging first if you can.
  3. If no fixed version is available to you, disable the Social Login module or the Apple and Facebook providers until one is.
  4. Review administrator and editor accounts for any you do not recognize, and check each account's linked social identities if your setup shows them.
  5. Force a password reset and sign out all sessions for privileged users if you see anything suspicious.
  6. Turn on two-factor authentication for administrators and keep the number of admin accounts small.
  7. If you use the BuddyBoss App JWT component, consider rotating its tokens or secrets after updating.
Caution. Disabling social login will stop members from signing in with Apple or Facebook. Warn your users first and make sure they have a password or another way in.

Detection and monitoring

The research does not describe indicators of compromise, so treat these as general review steps rather than confirmed signatures. Look at your web server access logs for unusual POST requests to REST routes related to social login, especially from addresses that then access the admin area. This read-only search shows REST API requests in a standard access log; adjust the path to your server.

Search an access log for REST API POST requests (adjust log path to your server)Shell
grep -i "POST /wp-json/" /var/log/nginx/access.log | tail -n 200

Also check for new users, role changes, newly installed plugins or modified files after any suspicious login. Our guides on checking whether a website is hacked and what to do if it is cover the follow-up. A website firewall can add a layer of filtering for login-related endpoints, but it is not a replacement for updating; see what a WAF is.

What we do not know yet

  • Whether the flaw is being exploited in the wild. The research does not say, and the CISA KEV field is empty.
  • Which version fixes it. The advisory lists patched versions as unknown.
  • Whether Apple, Facebook or both are exploitable in every configuration. The advisory describes both as affected token types.

Only one independent publisher (the advisory database record) covers this so far, and the NVD page repeats it, so details may change. We will treat the facts above as provisional until the vendor confirms them.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-80188 - GitHub Advisory Databasegithub.com
  2. CVE-2026-80188: The BuddyBoss Addons plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in versions up to, and including, 1.2.1.nvd.nist.gov ·
  • WordPress
  • BuddyBoss
  • CVE-2026-80188
  • Authentication bypass
  • Social login