Skip to main content
Menu
CVEs

BuddyBoss Addons account takeover in social login via unverified tokens

Affects BuddyBoss Addons 1.2.1 and earlier with the Social Login module in use. No fixed version is listed in the checked facts.

CVE-2026-80188Published , updated

9.8CriticalCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Summary

The BuddyBoss Addons plugin for WordPress accepts unverified Apple and Facebook identity tokens in its Social Login feature, so a remote attacker without a login can link their own provider identity to any existing account, including administrator accounts, if they know the user's email address. The attacker can then sign in as that user and take over the account.

Written by a model

Original description

The BuddyBoss Addons plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in versions up to, and including, 1.2.1. This is due to the Social Login REST endpoint trusting unverified Apple and Facebook identity-token claims and linking an attacker-controlled provider identifier to an existing WordPress user selected by the token’s email claim. This makes it possible for unauthenticated attackers who know a user’s email address to associate their provider identity with that account, including administrator accounts, and subsequently authenticate as the victim. Successful exploitation requires the BuddyBoss Platform plugin to be installed and active, with the Social Login module and selected provider enabled and configured. On sites with the separate BuddyBoss App JWT component, the vulnerable REST request can return an application token immediately.

Who should check

Teams running BuddyBoss Addons with the Social Login module enabled

“Bug: Social Login - Fixed a security issue affecting social login”

buddyboss.com

What to do

Workaround: While no fix is listed, limiting the affected feature is the available step, which means turning off the Social Login module if the plugin settings allow it. The checked facts give no other workaround.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-80188 (BuddyBoss Addons <= 1.2.1 - Unauthenticated Account Takeover via Unverified Social Login Identity Tokens), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-80188 (entry last updated 2026-11-20):
Affected:
- BuddyBoss BuddyBoss Addons: through 1.2.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- BuddyBoss Addons with the Social Login module in use (source: https://buddyboss.com/resources/buddyboss-addons/addons-1-2-2/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-80188 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-80188 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/9cb4a3f2-af99-473d-b70e-1ea1afca23ff?source=cve
- https://buddyboss.com/resources/buddyboss-addons/addons-1-2-2/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-80188
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-80188"}.

Affected versions

cve.now Index

35Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 40 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  5. Record last updated

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkbuddyboss.com · resources/buddyboss-addons/addons-1-2-2
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-80188
RecordNVD · CVE-2026-80188
Other links 1
Linkwordfence.com · threat-intel/vulnerabilities/id/9cb4a3f2-af99-473d-b70e-1ea1afca23ff?source=cve

Questions about CVE-2026-80188

Is CVE-2026-80188 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The advisory describes an unauthenticated account takeover caused by social login identity tokens that are not verified. The checked facts do not describe the exact steps an attacker would take.

Source: buddyboss.com

Which versions are affected by CVE-2026-80188?

BuddyBoss Addons: through 1.2.1.

Source: cve.now feed data

Am I affected, and how do I check?

Versions up to and including 1.2.1 of BuddyBoss Addons are in scope, but only where the Social Login module is in use. To check, look at the installed BuddyBoss Addons version on the WordPress plugins screen and check whether the Social Login module is enabled in the plugin's settings.

Source: buddyboss.com

How do I fix CVE-2026-80188?

The checked facts name no fixed version and no vendor patch identifiers, so the fix details are not available here. Check the vendor's advisory for a fixed version or patch identifiers before deciding what to install.

Source: buddyboss.com

What if there's no patch?

While no fix is listed, limiting the affected feature is the available step, which means turning off the Social Login module if the plugin settings allow it. The checked facts give no other workaround.

Source: buddyboss.com

No corrections so far. Something wrong on this page? Report an error.