# CVE-2026-89029: Blog2Social WordPress Plugin < 9.1.0 User Enumeration via AJAX Handler

> Low-privileged users can enumerate WordPress user accounts and map IDs to display names via an insecure AJAX handler in the Blog2Social plugin.

- **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:** 16 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-6r37-32vj-mjwv

## What is CVE-2026-89029?

CVE-2026-89029 is a medium-severity vulnerability in Adenion Blog2Social, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Adenion Blog2Social plugin for WordPress before 9.1.0 allows low-privileged users to enumerate WordPress user accounts. The b2s_get_select_mandant_user AJAX handler in includes/Ajax/Get.php resolves arbitrary user IDs supplied in the owner parameter to display names without verifying that the caller is authorized to read user account data, allowing any user with the edit_posts capability to map WordPress user IDs to display names and confirm account existence for arbitrary IDs.

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

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


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

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

## Is CVE-2026-89029 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89029 is a medium-severity vulnerability in Adenion Blog2Social, published on 16 Sep 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-89029 in the wild and no public exploit code.

Affected product: Adenion Blog2Social. 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-89029/ (Markdown: https://insights.sbomify.com/CVE-2026-89029/index.md)
```

## Sources

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

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