How severe is GHSA-8wx3-8m4x-g5h4?

No CVSS score has been assigned to GHSA-8wx3-8m4x-g5h4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8wx3-8m4x-g5h4?

GHSA-8wx3-8m4x-g5h4 affects the following packages: friendsofsymfony/user-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-8wx3-8m4x-g5h4?

Update friendsofsymfony/user-bundle to 1.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8wx3-8m4x-g5h4 is resolved across your whole dependency graph.

How do I detect GHSA-8wx3-8m4x-g5h4 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for friendsofsymfony/user-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8wx3-8m4x-g5h4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-8wx3-8m4x-g5h4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8wx3-8m4x-g5h4 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-8wx3-8m4x-g5h4 published, and has it been updated?

GHSA-8wx3-8m4x-g5h4 was published on May 15, 2024 and was last updated on July 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

FOSUserBundle User Identity Validation Vulnerability

Real-World Exposure

1 pkg affected

🐘friendsofsymfony/user-bundle

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Versions of FOSUserBundle prior to 1.2.1 have been found to be vulnerable to a security issue related to user identity validation. Specifically, user refreshing was performed using the primary key instead of the username, leading to a potential security risk if a user is allowed to change their username. The fix in version 1.2.1 addresses this issue by loading the user using the primary key during refreshing.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`friendsofsymfony/user-bundle`	≥ 1.0.0&&< 1.2.1	1.2.1`composer require friendsofsymfony/user-bundle:^1.2.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for friendsofsymfony/user-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update friendsofsymfony/user-bundle to 1.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8wx3-8m4x-g5h4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Versions of FOSUserBundle prior to 1.2.1 have been found to be vulnerable to a security issue related to user identity validation. Specifically, user refreshing was performed using the primary key instead of the username, leading to a potential security risk if a user is allowed to change their username. The fix in version 1.2.1 addresses this issue by loading the user using the primary key during refreshing.

O3 Security · Impact-Aware SCA

Is GHSA-8wx3-8m4x-g5h4 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

FOSUserBundle User Identity Validation VulnerabilityGHSA-8wx3-8m4x-g5h4