# CVE-2025-5526: BuddyPress Docs < 2.2.5 - Subscriber+ Arbitrary Document Read/Update

> A logged-in user can view and modify documents belonging to other users due to missing access controls in the BuddyPress Docs plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A: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:** 27 Jun 2025
- **Updated:** 1 Jul 2025
- **Also known as:** GHSA-h646-fcwc-rq3q

## What is CVE-2025-5526?

CVE-2025-5526 is a medium-severity missing authorization vulnerability in Unknown BuddyPress Docs, published on 27 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The BuddyPress Docs WordPress plugin before 2.2.5 lacks proper access controls and allows a logged in user to view and download files belonging to another user

## Which versions are affected by CVE-2025-5526?

It affects 1 product.


Products: Boonebgorges Buddypress Docs.

## How do I fix CVE-2025-5526?

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

## Is CVE-2025-5526 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5526 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5526 and fix it if it is affected.

What it is: CVE-2025-5526 is a medium-severity missing authorization vulnerability in Unknown BuddyPress Docs, published on 27 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5526 exists.

Affected product: Unknown BuddyPress Docs. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2025-5526/ (Markdown: https://insights.sbomify.com/CVE-2025-5526/index.md)
```

## Sources

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

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