CVE
BuddyPress unauthenticated exposure of private group activity
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
BuddyPress, a WordPress plugin, is affected. An attacker can remotely, without logging in, read private group activity content by iterating through activity IDs.
Original description
The BuddyPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 14.5.0. This is due to missing authorization checks in the bp_nouveau_ajax_get_single_activity_content AJAX handler. The function only verifies a nonce that is publicly exposed to any visitor who loads a BuddyPress page, but does not call bp_activity_user_can_read() to verify the user has permission to view the activity. This makes it possible for unauthenticated attackers to read private group activity content by iterating activity IDs.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
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-1214 (BuddyPress <= 14.5.0 - Missing Authorization to Unauthenticated Sensitive Information Exposure), 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-1214 (entry last updated 2026-11-18):
Affected:
- buddypress BuddyPress: through 14.5.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-1214 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-1214 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/36ec572d-45f1-45e1-a047-9472caac2578?source=cve
- https://plugins.trac.wordpress.org/browser/buddypress/tags/14.4.0/bp-templates/bp-nouveau/includes/activity/ajax.php#L289
- https://plugins.trac.wordpress.org/browser/buddypress/tags/14.4.0/bp-templates/bp-nouveau/buddypress-functions.php#L525
- https://plugins.trac.wordpress.org/changeset/3627603/
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-1214
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-1214"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- buddypress BuddyPress
through 14.5.0
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-1214 |
| Record | NVD · CVE-2026-1214 |
| Other links 4 | |
| Link | wordfence.com · threat-intel/vulnerabilities/id/36ec572d-45f1-45e1-a047-9472caac2578?source=cve |
| Link | plugins.trac.wordpress.org · browser/buddypress/tags/14.4.0/bp-templates/bp-nouveau/includes/activity/ajax.php#L289 |
| Link | plugins.trac.wordpress.org · browser/buddypress/tags/14.4.0/bp-templates/bp-nouveau/buddypress-functions.php#L525 |
| Link | plugins.trac.wordpress.org · changeset/3627603 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-1214
Is CVE-2026-1214 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
Which versions are affected by CVE-2026-1214?
BuddyPress: through 14.5.0.Source: cve.now feed data