# CVE-2026-5144: BuddyPress Groupblog <= 1.9.3 - Authenticated (Subscriber+) Privilege Escalation to Administrator via Group Blog IDOR

> Authenticated attackers can escalate privileges to Administrator on the main site of a Multisite network via insecure group blog settings.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 11 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-mxm6-xwqw-p92f

## What is CVE-2026-5144?

CVE-2026-5144 is a high-severity vulnerability in boonebgorges BuddyPress Groupblog, published on 11 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The BuddyPress Groupblog plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.9.3. This is due to the group blog settings handler accepting the `groupblog-blogid`, `default-member`, and `groupblog-silent-add` parameters from user input without proper authorization checks. The `groupblog-blogid` parameter allows any group admin (including Subscribers who create their own group) to associate their group with any blog on the Multisite network, including the main site (blog ID 1). The `default-member` parameter accepts any WordPress role, including `administrator`, without validation against a whitelist. When combined with `groupblog-silent-add`, any user who joins the attacker's group is automatically added to the targeted blog with the injected role. This makes it possible for authenticated attackers, with Subscriber-level access and above, to escalate any user (including themselves via a second account) to Administrator on the main site of the Multisite network.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-5144 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5144 is a high-severity vulnerability in boonebgorges BuddyPress Groupblog, published on 11 Apr 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-5144 in the wild and no public exploit code.

Affected product: boonebgorges BuddyPress Groupblog. 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-2026-5144/ (Markdown: https://insights.sbomify.com/CVE-2026-5144/index.md)
```

## Sources

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

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