# DRUPAL-CONTRIB-2018-027: This module adds a new formatter for the file fields, which allows any file extension to be uploaded.

> Authenticated users with upload permissions can bypass sanitization to upload malicious SVG files, potentially leading to code execution.

- **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:** 9 May 2018

## What is DRUPAL-CONTRIB-2018-027?

DRUPAL-CONTRIB-2018-027 is a vulnerability in drupal/svg_formatter, published on 9 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This module adds a new formatter for the file fields, which allows any file extension to be uploaded.  
The module doesn't sufficiently handle sanitization under the scenario uploaded SVG files.  
This vulnerability is mitigated by the fact that an attacker must have a role with the permission create or edit on certain content types that allows SVG files to be uploaded.

## Which versions are affected by DRUPAL-CONTRIB-2018-027?


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

## How do I fix DRUPAL-CONTRIB-2018-027?

Apply the vendor's patch.

## Is DRUPAL-CONTRIB-2018-027 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2018-027 is a vulnerability in drupal/svg_formatter, published on 9 May 2018. 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-2018-027 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2018-027

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