# CVE-2026-93662: Events Manager 7.4.1 - 7.4.4 - Subscriber+ Unpublished Event and Location Disclosure via 'owner' Parameter

> Low-privileged users can read unpublished event and location details, including addresses, by manipulating the owner parameter in Events Manager.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-wvr6-m4wg-qf6q

## What is CVE-2026-93662?

CVE-2026-93662 is a medium-severity missing authorization vulnerability in Unknown Events Manager, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Events Manager  WordPress plugin before 7.4.5 does not force the scope of its logged-in event and location search when a caller supplies their own owner value, letting a low-privileged user read other accounts' unpublished, pending or trashed event and venue content, including full street addresses.

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

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


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

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

## Is CVE-2026-93662 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93662 is a medium-severity missing authorization vulnerability in Unknown Events Manager, published on 24 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-93662 in the wild and no public exploit code.

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

## Sources

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

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