Drupal Core Link Fields: Unsanitized Attributes Allow XSS

Published as "Drupal Core Cross-Site Scripting (XSS) Vulnerability"

low Drupal · Last reviewed Nov 8, 2026

CVE: CVE-2025-31675
GHSA: GHSA-m4wj-hhwj-47qp
Packagist: PKSA-42zc-x5ss-z64p
Reported: Apr 1, 2025

Lets a user who can set Link field attributes run script in other visitors' browsers on Drupal sites that use Link fields.

Affected and fixed versions

In drupal/core. Find the row for the version you run, and update to the release next to it.

If you run	Update to	Support
11.1.0 – 11.1.4	11.1.5
11.0.0 – 11.0.12	11.0.13
10.4.0 – 10.4.4	10.4.5

Show 1 older branch

8.0.0 – 10.3.13

10.3.14

Upgrade

Run the line for the branch you are on.

composer require drupal/core:^11.1.5
composer require drupal/core:^11.0.13
composer require drupal/core:^10.4.5

What this means

Drupal core didn't clean the attributes on Link fields well enough. A user who can set those attributes can make the site run their script in other visitors' browsers (cross-site scripting, or XSS). See Drupal's advisory.

Who is affected

Sites on an affected version of drupal/core that use the core Link module with at least one link field. The attacker also needs a way to add specific attributes to a link field. Drupal says that usually means edit access through core's web services, or through a contributed or custom module.

Sites with the Link module turned off, or with no link fields, aren't affected.

What to do

Update to the fixed release for your branch:

Drupal 10.3: update to 10.3.14
Drupal 10.4: update to 10.4.5
Drupal 11.0: update to 11.0.13
Drupal 11.1: update to 11.1.5

Drupal releases before 10.3 no longer get security fixes from the Drupal Security Team, so move to a supported branch.

Reported by Samuel Mortenson.

Check your app with an agent

Paste this into a coding agent that can read your project, such as Claude Code, Codex or Amp. It checks your composer.lock against the versions above and tells you what to update, without changing anything.

Check whether the PHP project you have access to is affected by this security advisory, and tell me what to update. Do a read-only check: don't edit files, don't run composer update or composer require, and don't try to reproduce the flaw.

Advisory: Drupal Core Link Fields: Unsanitized Attributes Allow XSS (CVE-2025-31675, GHSA-m4wj-hhwj-47qp)
Details: https://phpnews.net/security/drupal/ghsa-m4wj-hhwj-47qp

Affected versions, as Composer constraints:
- drupal/core: >=11.1.0,<11.1.5|>=11.0.0,<11.0.13|>=10.4.0,<10.4.5|>=8.0.0,<10.3.14

Fixed releases:
- 11.1.0 – 11.1.4: update to 11.1.5
- 11.0.0 – 11.0.12: update to 11.0.13
- 10.4.0 – 10.4.4: update to 10.4.5

1. Find every composer.lock in the project outside vendor/ (a monorepo can have one per app) and read the installed version of each package above. Packages installed as dependencies of other packages count too.
2. Compare each installed version with its constraint: "|" separates alternative ranges, and "," means both bounds apply.
3. For each affected install, read "What this means" at https://phpnews.net/security/drupal/ghsa-m4wj-hhwj-47qp and check whether the project meets the conditions it describes (a feature in use, a config value, a driver). Say which conditions you could check and which you couldn't.
4. Report a table: lock file | package | installed version | affected (yes, no or unknown) | conditions met (yes, no or unknown) | update to | evidence. For each affected package, give the command that would fix it, without running it: composer update <package> --with-dependencies when it is only installed as a dependency of another package, or composer require with the fixed version when composer.json requires it directly. If the installed version is on a branch with no fixed release listed, say it needs a move to a newer branch.

Sources

← All Drupal advisories