# DRUPAL-CONTRIB-2023-041: This module makes PatternLab's custom Twig functions available to Drupal theming.

> Insufficient filtering in example code allows XSS if copied to a theme, requiring site builders to update the module.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Aug 2023

## What is DRUPAL-CONTRIB-2023-041?

DRUPAL-CONTRIB-2023-041 is a cross-site scripting vulnerability in drupal/unified_twig_ext, published on 30 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This module makes PatternLab's custom Twig functions available to Drupal theming.

The module's included examples don't sufficiently filter data.

This vulnerability is mitigated by the fact that the included examples must have been copied to a site's theme.

## Which versions are affected by DRUPAL-CONTRIB-2023-041?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/unified_twig_ext` | Packagist:https://packages.drupal.org/8 | All versions | 1.1.1 |

## How do I fix DRUPAL-CONTRIB-2023-041?

Apply the vendor's patch.

## Is DRUPAL-CONTRIB-2023-041 being exploited?

There is no known exploitation of DRUPAL-CONTRIB-2023-041 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CONTRIB-2023-041 and fix it if it is affected.

What it is: DRUPAL-CONTRIB-2023-041 is a cross-site scripting vulnerability in drupal/unified_twig_ext, published on 30 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2023-041 in the wild and no public exploit code.

Affected product: drupal/unified_twig_ext. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/DRUPAL-CONTRIB-2023-041/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2023-041/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2023-041

---
From sbomify Insights: https://insights.sbomify.com/DRUPAL-CONTRIB-2023-041/
Summaries are generated and may contain mistakes; the official description above is the record.