# DRUPAL-CONTRIB-2019-066: This module enables you to have a separate permission only for creating users.

> An attacker can bypass administrator approval requirements to create user accounts when specific registration settings are enabled.

- **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:** 18 Sep 2019

## What is DRUPAL-CONTRIB-2019-066?

DRUPAL-CONTRIB-2019-066 is an authentication bypass vulnerability in drupal/create_user_permission, published on 18 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This module enables you to have a separate permission only for creating users.

The module doesn't respect Drupal's setting for "Who can register accounts?" when set to "Visitors, but administrator approval is required".

When this option is chosen, the module overrides the setting, and makes it possible to register accounts with no approval.

This vulnerability can be mitigated by having other settings in place for account registration, such as requiring email verification for new accounts, or permitting account creation for "Administrators only".

## Which versions are affected by DRUPAL-CONTRIB-2019-066?


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

## How do I fix DRUPAL-CONTRIB-2019-066?

Change a configuration setting.

## Is DRUPAL-CONTRIB-2019-066 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2019-066 is an authentication bypass vulnerability in drupal/create_user_permission, published on 18 Sep 2019. 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-2019-066 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2019-066

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