# CVE-2026-112355: MembershipWorks WordPress Plugin < 6.17 Information Disclosure via WordPress REST API


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-hvvh-f79h-xxpp

## What is CVE-2026-112355?

CVE-2026-112355 is a high-severity vulnerability in MembershipWorks, published on 27 Oct 2026. 

### Official description

The MembershipWorks plugin for WordPress before 6.17 contains an information disclosure vulnerability that allows unauthenticated attackers to access member-only content through the WordPress REST API. Because the filter that strips protected content for non-members is only attached during normal front-end request handling and not during REST API requests, an unauthenticated attacker can retrieve the raw member-only content in a post or page’s rendered content, bypassing the plugin’s content protection.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-112355 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112355 is a high-severity vulnerability in MembershipWorks, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112355 in the wild and no public exploit code.

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

## Sources

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

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