# CVE-2026-11871: Team Showcase Supreme < 9.3 - Unauthenticated Sensitive Data Disclosure via wpm_6310_team_member_details

> Unauthenticated attackers can enumerate and disclose private team member details, including emails and phone numbers, via an unprotected AJAX action.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-j3f9-r5x4-pr68

## What is CVE-2026-11871?

CVE-2026-11871 is a medium-severity vulnerability in Unknown Team Members, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Team Members WordPress plugin before 9.3 does not perform any authorization or visibility check in an unauthenticated AJAX action that returns full team member records by ID, allowing unauthenticated attackers to enumerate and disclose details, including email addresses and phone numbers, of team members the administrator has not published publicly.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-11871 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11871 is a medium-severity vulnerability in Unknown Team Members, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11871 in the wild and no public exploit code.

Affected product: Unknown Team Members. 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-11871/ (Markdown: https://insights.sbomify.com/CVE-2026-11871/index.md)
```

## Sources

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

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