Symfony UX allows unsanitized HTML attribute injection via ComponentAttributes

Exploitation

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

CVSS

6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2025-47946: 0.25% estimated exploitation activity in the next 30 days; percentile 16.76 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Rendering {{ attributes }} or using any method that returns a ComponentAttributes instance (e.g. only(), defaults(), without()) ouputs attribute values directly without escaping. If these values are unsafe (e.g. contain user input), this can lead to HTML attribute injection and XSS vulnerabilities. Patches The issue is fixed in version 2.25.1 of symfony/ux-twig-component by using Twig's EscaperRuntime to properly escape HTML attributes in ComponentAttributes. If you use symfony/ux-live-component, you must also update it to 2.25.1 to benefit from the fix, as it reuses the ComponentAttributes class internally. Workarounds Until you can upgrade, avoid rendering {{ attributes }} or derived objects directly if it may contain untrusted values. Instead, use {{ attributes.render('name') }} for safe output of individual attributes. References GitHub repository: symfony/ux

Published by the source

19 May 2025, 22:24 UTC

Last modified by the source

29 Aug 2025, 21:08 UTC

Source last checked

26 Oct 2026, 14:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5j3w-5pcr-f8hg

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

# Patch Next advisory brief: CVE-2025-47946

Advisory: Symfony UX allows unsanitized HTML attribute injection via ComponentAttributes
IDs: CVE-2025-47946, GHSA-5j3w-5pcr-f8hg
Record: https://patchnext.com/advisories/cve-2025-47946 (revision 1, source checked 26 Oct 2026, 14:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: symfony/ux-live-component 2.25.1; symfony/ux-twig-component 2.25.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist symfony/ux-live-component: affected < 2.25.1; fixed in 2.25.1
- Packagist symfony/ux-twig-component: affected < 2.25.1; fixed in 2.25.1

## Suggested inspection (read-only)
- Packagist symfony/ux-live-component: check the installed version with your package manager.
- Packagist symfony/ux-twig-component: 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/ux-live-component, symfony/ux-twig-component.
- 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-5j3w-5pcr-f8hg (GitHub-reviewed advisory GHSA-5j3w-5pcr-f8hg lists affected ranges: Packagist symfony/ux-twig-component >=0 =0 <2.25.1)

Commands are suggestions: review each one before running it.