# CVE-2026-15246: RealHomes Memberships < 3.1.0 - Subscriber+ Membership Payment Bypass

> Authenticated users can bypass payment verification to obtain paid membership packages without paying in RealHomes Memberships plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-qgvv-r5pp-fcw2

## What is CVE-2026-15246?

CVE-2026-15246 is a medium-severity vulnerability in Unknown RealHomes Memberships, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The RealHomes Memberships WordPress plugin before 3.1.0 does not verify that a membership payment actually completed, nor check a nonce or the user's capability, before granting a paid membership package, allowing any authenticated user such as a Subscriber to obtain paid membership packages without paying.

Weakness: CWE-862 (Missing Authorization), CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-15246 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15246 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15246 is a medium-severity vulnerability in Unknown RealHomes Memberships, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15246 exists.

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

## Sources

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

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