# FOSUserBundle User Identity Validation Vulnerability

Advisory record · `GHSA-8wx3-8m4x-g5h4`

- **Identifiers:** `GHSA-8wx3-8m4x-g5h4` · `PKSA-9y6m-pqt9-vrds`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-285](https://cwe.mitre.org/data/definitions/285.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 15 May 2024
- **Updated:** 16 Jul 2026
- **Reviewed by a person:** No

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

## Affected packages

- `friendsofsymfony/user-bundle` (Packagist): affected `>=1.0.0, <1.2.1`; fixed in `1.2.1`

## Machine-written summary

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

> FOSUserBundle versions from 1.0.0 before 1.2.1 are affected. User refreshing used the primary key rather than the username, which poses a risk where users are allowed to change their username. The source gives few details about the exact attack or what an attacker could do. Upgrade to friendsofsymfony/user-bundle 1.2.1 or later.

Written 3 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

No source has published a CVSS score for this record yet.

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

## Timeline

- 31 Oct 2026, 14:25 UTC: First seen by agentprime
- 31 Oct 2026, 14:25 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8wx3-8m4x-g5h4)

## Sources

- [GitHub Advisory Database: GHSA-8wx3-8m4x-g5h4](https://github.com/advisories/GHSA-8wx3-8m4x-g5h4)
- [OSV: GHSA-8wx3-8m4x-g5h4](https://osv.dev/vulnerability/GHSA-8wx3-8m4x-g5h4)
- <https://github.com/FriendsOfSymfony/FOSUserBundle/commit/1b8bc18e3d99ef0b52b4141f20da323033d6be9b>
- <https://github.com/FriendsOfSymfony/FOSUserBundle/commit/5a36e2958068d1e6501dc8cf39bbae3ebb859d9f>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/friendsofsymfony/user-bundle/2012-07-10-1.yaml>
- <https://github.com/FriendsOfSymfony/FOSUserBundle>
- <https://github.com/FriendsOfSymfony/FOSUserBundle/blob/master/Changelog.md>

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-8wx3-8m4x-g5h4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8wx3-8m4x-g5h4/>. Everything for agents: <https://agentprime.io/llms.txt>.
