# DRUPAL-CONTRIB-2020-029: The Modal form module is a toolset for quick start of using forms in modal windows.

> Unauthenticated attackers can view and submit any form if they know the class name, bypassing intended access controls.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jul 2020

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

DRUPAL-CONTRIB-2020-029 is a missing authorization vulnerability in drupal/modal_form, published on 22 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Modal form module is a toolset for quick start of using forms in modal windows.

Any form is available for view and submit when the `modal_form` module is installed. The only requirement is to know the form's fully-qualified class name.

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


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

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

Upgrade to a fixed version.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2020-029 is a missing authorization vulnerability in drupal/modal_form, published on 22 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2020-029 in the wild and no public exploit code.

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

## Sources

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

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