# DRUPAL-CONTRIB-2020-004: The Profile module enables you to allow users to have configurable user profiles.

> Users with profile creation permissions can create profiles for any user due to insufficient access checks in the Drupal Profile module.

- **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:** No
- **Published:** 19 Feb 2020

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

DRUPAL-CONTRIB-2020-004 is a missing authorization vulnerability in drupal/profile, published on 19 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Profile module enables you to allow users to have configurable user profiles.

The module doesn't sufficiently check access when creating a user profile. Users with the "create profiles" permission could create profiles for any users.

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/profile` | Packagist:https://packages.drupal.org/8 | From 1.0.0 to 1.0.0 | None |

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

No fix has been published for DRUPAL-CONTRIB-2020-004 yet. Limit exposure of the affected software until one is available.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2020-004 is a missing authorization vulnerability in drupal/profile, published on 19 Feb 2020. 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-2020-004 in the wild and no public exploit code.

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

## Sources

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

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