# Silverstripe Missing security check on dev/build/defaults

Advisory record · `GHSA-x5w2-wcr8-9q45`

- **Identifiers:** `GHSA-x5w2-wcr8-9q45` · `PKSA-nvnj-5889-jzd9`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-425](https://cwe.mitre.org/data/definitions/425.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 23 May 2024
- **Updated:** 28 Nov 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 May 2024, 19:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `silverstripe/framework` (Packagist): affected `<3.1.17 || >=3.2.0, <3.2.2 || >=3.3.0-beta1, <3.3.0`; fixed in `3.1.17`, `3.2.2`, `3.3.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Silverstripe framework versions below 3.1.17, from 3.2.0 before 3.2.2, and from 3.3.0-beta1 before 3.3.0 are affected. The buildDefaults action on DevelopmentAdmin skips the login check that protects the /dev/build route in live mode, so an unauthenticated attacker can run it. This can modify database state and reveal which database tables exist. Upgrade silverstripe/framework to 3.1.17, 3.2.2, 3.3.0, or later.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:29 UTC: First seen by agentprime
- 31 Oct 2026, 14:29 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x5w2-wcr8-9q45)

## Sources

- [GitHub Advisory Database: GHSA-x5w2-wcr8-9q45](https://github.com/advisories/GHSA-x5w2-wcr8-9q45)
- [OSV: GHSA-x5w2-wcr8-9q45](https://osv.dev/vulnerability/GHSA-x5w2-wcr8-9q45)
- <https://github.com/silverstripe/silverstripe-framework/commit/15d4db3b4a7dbc9a7e089f9329a396f8408ed7d9>
- <https://github.com/silverstripe/silverstripe-framework/commit/3398f670d881447f8777b567f1ead7c0d8d253f5>
- <https://github.com/silverstripe/silverstripe-framework/commit/5d2fc0d7cac4ce686f7ae05c1a7b1ad8c01711a8>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2015-028-1.yaml>
- <https://github.com/silverstripe/silverstripe-framework>
- <https://www.silverstripe.org/download/security-releases/ss-2015-028>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x5w2-wcr8-9q45>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x5w2-wcr8-9q45/>. Everything for agents: <https://agentprime.io/llms.txt>.
