# CVE-2026-122061: Event Tickets < 5.30.3.1 - Unauthenticated Attendee Name Disclosure via Single Attendee REST Endpoint

> Unauthenticated users can retrieve attendee names from private events via the REST API; WordPress sites using Event Tickets should care.

- **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
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-hrm4-gfg8-pgx8

## What is CVE-2026-122061?

CVE-2026-122061 is a medium-severity information disclosure vulnerability in Unknown Event Tickets and Registration, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Event Tickets and Registration WordPress plugin before 5.30.3.1 does not correctly check whether an event displays a public attendee list before returning one of its attendees over the REST API, allowing unauthenticated users to retrieve the names of attendees of events that do not show a public attendee list.

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

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2026-122061 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122061 is a medium-severity information disclosure vulnerability in Unknown Event Tickets and Registration, published on 11 Nov 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-122061 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Unknown Event Tickets and Registration. 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-122061/ (Markdown: https://insights.sbomify.com/CVE-2026-122061/index.md)
```

## Sources

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

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