# DRUPAL-CONTRIB-2020-008: SVG Image module allows to upload SVG files.

> An attacker with upload permissions can inject malicious scripts via SVG files, leading to cross-site scripting attacks against other users.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Mar 2020

## What is DRUPAL-CONTRIB-2020-008?

DRUPAL-CONTRIB-2020-008 is a cross-site scripting vulnerability in drupal/svg_image, published on 25 Mar 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

SVG Image module allows to upload SVG files.

The module did not sufficiently protect against malicious code inside SVG files leading to a Cross Site Scripting vulnerability.

This vulnerability is mitigated by the fact that an attacker must have permission to upload an SVG file.

## Which versions are affected by DRUPAL-CONTRIB-2020-008?


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

## How do I fix DRUPAL-CONTRIB-2020-008?

Apply the vendor's patch.

## Is DRUPAL-CONTRIB-2020-008 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2020-008 is a cross-site scripting vulnerability in drupal/svg_image, published on 25 Mar 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2020-008 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2020-008

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