# CVE-2026-53675: BuddyPress 14.4.0 Friends List IDOR via REST API

> Authenticated attackers can enumerate other users' private friend lists via the REST API due to missing ownership checks in BuddyPress.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-wmjr-58rf-xgrc

## What is CVE-2026-53675?

CVE-2026-53675 is a medium-severity missing authorization vulnerability in BuddyPress, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

BuddyPress 14.4.0 contains an insecure direct object reference vulnerability in the friends REST API that allows any authenticated attacker to enumerate another user's complete friend list. Attackers can query the friends endpoint with an arbitrary user_id because the get_items_permissions_check method only verifies that the requester is logged in and never checks ownership of the requested list, resulting in disclosure of users' private social connections.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-53675?

2 open source packages ship an affected version, including buddypress/buddypress.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `buddypress/buddypress` | Packagist | All versions to 14.4.0 | None |
| `buddypress/buddypress` | Packagist | All versions to 14.4.0 | None |

## How do I fix CVE-2026-53675?

No fix has been published for CVE-2026-53675 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-53675 being exploited?

There is no known exploitation of CVE-2026-53675 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53675 and fix it if it is affected.

What it is: CVE-2026-53675 is a medium-severity missing authorization vulnerability in BuddyPress, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53675 in the wild and no public exploit code.

Affected packages and fixed versions:
- buddypress/buddypress (Packagist): affected all versions up to 14.4.0; no fix listed
- buddypress/buddypress (Packagist): affected all versions up to 14.4.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53675/ (Markdown: https://insights.sbomify.com/CVE-2026-53675/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53675
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53675
- OSV: https://osv.dev/vulnerability/CVE-2026-53675

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53675/
Summaries are generated and may contain mistakes; the official description above is the record.