# GHSA-r3pr-fh25-wrfc: silverstripe/framework's install.php script discloses sensitive data by pre-populating DB credential forms

> An unauthenticated attacker can view the source of the install.php script to extract pre-configured database credentials and default admin passwords.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2024

## What is GHSA-r3pr-fh25-wrfc?

GHSA-r3pr-fh25-wrfc is a vulnerability in silverstripe/framework, published on 27 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When accessing the `install.php` script it is possible to extract any pre-configured database or default admin account password by viewing the source of the page, and inspecting the `value` property of the password fields.

## Which versions are affected by GHSA-r3pr-fh25-wrfc?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | From 4.0.0-rc1 | 4.0.1 |
| `silverstripe/framework` | Packagist | From 4.0.0-rc1 | 4.0.1 |

## How do I fix GHSA-r3pr-fh25-wrfc?

Upgrade silverstripe/framework to 4.0.1 or later.

## Is GHSA-r3pr-fh25-wrfc being exploited?

There is no known exploitation of GHSA-r3pr-fh25-wrfc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-r3pr-fh25-wrfc and fix it if it is affected.

What it is: GHSA-r3pr-fh25-wrfc is a vulnerability in silverstripe/framework, published on 27 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-r3pr-fh25-wrfc in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.1
- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.1

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/GHSA-r3pr-fh25-wrfc/ (Markdown: https://insights.sbomify.com/GHSA-r3pr-fh25-wrfc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-r3pr-fh25-wrfc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-r3pr-fh25-wrfc/
Summaries are generated and may contain mistakes; the official description above is the record.