# CVE-2022-0287: Mycred < 2.4.4.1 - Subscriber+ User E-mail Addresses Disclosure

> Authenticated users can retrieve all email addresses from the blog due to missing authorization in the myCred 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:** 25 Apr 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9q9g-fwr6-596x

## What is CVE-2022-0287?

CVE-2022-0287 is a medium-severity missing authorization vulnerability in Unknown myCred, published on 25 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The myCred WordPress plugin before 2.4.4.1 does not have any authorisation in place in its mycred-tools-select-user AJAX action, allowing any authenticated user, such as subscriber to call and retrieve all email addresses from the blog

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-0287?

It affects 1 product.


Products: Wpexperts Mycred.

## How do I fix CVE-2022-0287?

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

## Is CVE-2022-0287 being exploited?

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

## Other vulnerabilities in Unknown myCred

- [CVE-2021-24755](https://insights.sbomify.com/CVE-2021-24755/): myCred < 2.3 - Subscriber+ SQL Injection (high 8.8)
- [CVE-2023-47853](https://insights.sbomify.com/CVE-2023-47853/): WordPress myCred Plugin <= 2.6.1 is vulnerable to Cross Site Scripting (XSS) (medium 6.5)
- [CVE-2023-35096](https://insights.sbomify.com/CVE-2023-35096/): WordPress myCred Plugin <= 2.5 is vulnerable to Cross Site Request Forgery (CSRF) (medium 5.4)
- [CVE-2024-43214](https://insights.sbomify.com/CVE-2024-43214/): WordPress myCred plugin <= 2.7.2 - Sensitive Data Exposure vulnerability (medium 5.3)
- [CVE-2022-0363](https://insights.sbomify.com/CVE-2022-0363/): myCred < 2.4.4 - Subscriber+ Arbitrary Post Creation (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0287 and fix it if it is affected.

What it is: CVE-2022-0287 is a medium-severity missing authorization vulnerability in Unknown myCred, published on 25 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0287 in the wild and no public exploit code.

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

## Sources

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

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