# CVE-2015-9435: Weak cryptography in n/a

> The WordPress oauth2-provider plugin uses weak random number generation, potentially allowing attackers to bypass authentication or predict tokens.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hf64-c32f-4gj5

## What is CVE-2015-9435?

CVE-2015-9435 is a critical vulnerability in n/a, published on 26 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The oauth2-provider plugin before 3.1.5 for WordPress has incorrect generation of random numbers.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2015-9435?

It affects 1 product.


Products: Dash10 Oauth Server.

## How do I fix CVE-2015-9435?

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

## Is CVE-2015-9435 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-3894](https://insights.sbomify.com/CVE-2022-3894/): WP OAuth Server < 4.2.5 - Arbitrary Post Deletion via CSRF (medium 4.3)
- [CVE-2022-4148](https://insights.sbomify.com/CVE-2022-4148/): WP OAuth Server < 4.3.0 - Subscriber+ Arbitrary Client Deletion (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-9435 and fix it if it is affected.

What it is: CVE-2015-9435 is a critical vulnerability in n/a, published on 26 Sep 2019. 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-2015-9435 in the wild and no public exploit code.

Affected product: n/a. 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-2015-9435/ (Markdown: https://insights.sbomify.com/CVE-2015-9435/index.md)
```

## Sources

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

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