# DRUPAL-CONTRIB-2019-092: The Smart Trim module allows site builders additional control with text summary fields.

> Authenticated users with content creation rights can inject scripts via insufficient filtering in the Smart Trim module when specific options are enabled.

- **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:** 11 Dec 2019

## What is DRUPAL-CONTRIB-2019-092?

DRUPAL-CONTRIB-2019-092 is a cross-site scripting vulnerability in drupal/smart_trim, published on 11 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Smart Trim module allows site builders additional control with text summary fields.

The module doesn't sufficiently filter text when certain options are selected.

This vulnerability is mitigated by the fact that an attacker must have a role with the ability to create content on the site when certain options are selected for the trimmed output.

## Which versions are affected by DRUPAL-CONTRIB-2019-092?


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

## How do I fix DRUPAL-CONTRIB-2019-092?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2019-092 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2019-092 is a cross-site scripting vulnerability in drupal/smart_trim, published on 11 Dec 2019. 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-2019-092 in the wild and no public exploit code.

Affected product: drupal/smart_trim. 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-2019-092/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2019-092/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2019-092

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