# DRUPAL-CONTRIB-2022-040: The Wingsuit module enables site builders to build UI Patterns (and|or) Twig Components with Storybook and use them without any mapping code in Drupal.

> An attacker can view and modify Wingsuit configuration due to missing access checks on the admin form.

- **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:** 18 May 2022

## What is DRUPAL-CONTRIB-2022-040?

DRUPAL-CONTRIB-2022-040 is a missing authorization vulnerability in drupal/wingsuit_companion, published on 18 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Wingsuit module enables site builders to build UI Patterns (and|or) Twig Components with Storybook and use them without any mapping code in Drupal.

The module doesn't have an access check for the admin form allowing an attacker to view and modify the Wingsuit configuration.

## Which versions are affected by DRUPAL-CONTRIB-2022-040?


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

## How do I fix DRUPAL-CONTRIB-2022-040?

Apply the vendor's patch.

## Is DRUPAL-CONTRIB-2022-040 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2022-040 is a missing authorization vulnerability in drupal/wingsuit_companion, published on 18 May 2022. 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-2022-040 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2022-040

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