# DRUPAL-CONTRIB-2023-032: Carefully crafted input by an attacker will not be sanitized by this module, which can result in a script injection.

> Attackers can inject scripts through unsanitized input in the DRUPAL CMS module; sites using it should care.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** Yes
- **Published:** 26 Jul 2023

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

DRUPAL-CONTRIB-2023-032 is a cross-site scripting vulnerability in drupal/minifyhtml, published on 26 Jul 2023. 

### Official description

Carefully crafted input by an attacker will not be sanitized by this module, which can result in a script injection.

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

An affected version is exposed as installed. No special setting or call is needed.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/minifyhtml` | Packagist:https://packages.drupal.org/8 | All versions | 1.13.0, 2.0.3 |

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

No fix published yet.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2023-032 is a cross-site scripting vulnerability in drupal/minifyhtml, published on 26 Jul 2023. 
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2023-032 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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

## Sources

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

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