Symfony may allow a user to switch to using another user's identity

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Symfony 2.0.6 has just been released. It addresses a security vulnerability in the EntityUserProvider as provided in the Doctrine bridge. If you let your users update their login/username from a form, and if you are using Doctrine as a user provider, then you are vulnerable and you should upgrade as soon as possible. The issue is that it is possible for a user to switch to another one. Here is how to reproduce it: The current user changes its username via a form to another existing username. When the form is submitted, he will have a validation error (as the username already exists) but the user object in the session will still be modified to the new username. This user from the session will be used for the next requests and so the user will be switched to this other user. The fix is to always refresh the user via the primary key (which cannot be updated via a form) instead of the username. If you cannot upgrade immediately, please apply the following patch:…

Published by the source

30 May 2024, 00:56 UTC

Last modified by the source

30 May 2024, 00:56 UTC

Source last checked

26 Oct 2026, 14:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7mx2-7q8p-pgmw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-7mx2-7q8p-pgmw

Advisory: Symfony may allow a user to switch to using another user's identity
IDs: GHSA-7mx2-7q8p-pgmw
Record: https://patchnext.com/advisories/ghsa-7mx2-7q8p-pgmw (revision 1, source checked 26 Oct 2026, 14:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: symfony/symfony 2.0.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist symfony/symfony: affected >= 2.0.0, < 2.0.6; fixed in 2.0.6

## Suggested inspection (read-only)
- Packagist symfony/symfony: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on symfony/symfony.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7mx2-7q8p-pgmw (GitHub-reviewed advisory GHSA-7mx2-7q8p-pgmw lists affected ranges: Packagist symfony/symfony >=2.0.0 <2.0.6)

Commands are suggestions: review each one before running it.