# CVE-2024-7648: Opal Membership <= 1.2.4 - Authenticated (Subscriber+) Information Disclosure

> Authenticated subscribers can view private payment notes intended for administrators due to improper access controls in the Opal Membership 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:** 10 Aug 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-r9vj-m6q6-fgw4

## What is CVE-2024-7648?

CVE-2024-7648 is a medium-severity vulnerability in wpopal Opal Membership, published on 10 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Opal Membership plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.2.4 via the private notes functionality on payments which utilizes WordPress comments. This makes it possible for authenticated attackers, with subscriber-level access and above, to view private notes via recent comments that should be restricted to just administrators.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-7648?


## How do I fix CVE-2024-7648?

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

## Is CVE-2024-7648 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7648 and fix it if it is affected.

What it is: CVE-2024-7648 is a medium-severity vulnerability in wpopal Opal Membership, published on 10 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7648 in the wild and no public exploit code.

Affected product: wpopal Opal Membership. 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-2024-7648/ (Markdown: https://insights.sbomify.com/CVE-2024-7648/index.md)
```

## Sources

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

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