# CVE-2026-18035: User Access Manager < 2.3.15 - Unauthenticated Restricted Content Disclosure via REST API

> Unauthenticated attackers can bypass access restrictions to read restricted content via the REST API in the User Access Manager plugin.

- **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:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-x37j-q2h4-mfmw

## What is CVE-2026-18035?

CVE-2026-18035 is a medium-severity missing authorization vulnerability in Unknown User Access Manager, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The User Access Manager WordPress plugin before 2.3.15 does not apply its access restrictions to REST API requests, allowing unauthenticated attackers to read the content of posts, pages and custom post types that have been restricted to specific user groups.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-18035 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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