# CVE-2023-32302: Silverstripe Framework: Members with no password can be created and bypass custom login forms


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 1 Aug 2023
- **Updated:** 4 Oct 2023
- **Also known as:** GHSA-36xx-7vf6-7mv3

## What is CVE-2023-32302?

CVE-2023-32302 is a vulnerability in silverstripe/framework, published on 1 Aug 2023. 

### Official description

Authoritative user requested CVE rejection
https://github.com/github/advisory-database/pull/2575#issuecomment-1745811653

## Which versions are affected by CVE-2023-32302?

4 open source packages ship an affected version, including silverstripe/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | From 3.0.0 | 4.13.14 |
| `silverstripe/framework` | Packagist | From 3.0.0 | 4.13.14 |
| `silverstripe/framework` | Packagist | From 5.0.0 | 5.0.13 |
| `silverstripe/framework` | Packagist | From 5.0.0 | 5.0.13 |

## How do I fix CVE-2023-32302?

Upgrade silverstripe/framework to a fixed version for your release line: 4.13.14 or 5.0.13.

## Is CVE-2023-32302 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32302 and fix it if it is affected.

What it is: CVE-2023-32302 is a vulnerability in silverstripe/framework, published on 1 Aug 2023. 
Exploitation: There is no known exploitation of CVE-2023-32302 in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected from 3.0.0; fixed in 4.13.14
- silverstripe/framework (Packagist): affected from 3.0.0; fixed in 4.13.14
- silverstripe/framework (Packagist): affected from 5.0.0; fixed in 5.0.13
- silverstripe/framework (Packagist): affected from 5.0.0; fixed in 5.0.13

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-2023-32302/ (Markdown: https://insights.sbomify.com/CVE-2023-32302/index.md)
```

## Sources

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

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