# CVE-2026-18365: Zportals < 6.4.2 - Subscriber+ User Email Disclosure

> Subscribers can view all registered users' emails and names due to missing authorization checks in the Zportals WordPress plugin.

- **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:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-xr35-jw5p-9pmm

## What is CVE-2026-18365?

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

### Official description

The zportals WordPress plugin before 6.4.2 does not perform any capability or nonce check on one of its AJAX actions, allowing users with a subscriber-level account to disclose the display name and email address of every registered user, including administrators.

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

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


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

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

## Is CVE-2026-18365 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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