dbcve.org
Registration RoleDrupal extension · Registration Role Project

CVE-2024-13251

HIGH · 8.8 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 2.0.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Incorrect Privilege Assignment vulnerability in Drupal Registration role allows Privilege Escalation.This issue affects Registration role: from 0.0.0 before 2.0.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Drupal Registration module has an incorrect privilege assignment vulnerability in the Registration role that allows privilege escalation. Users assigned the Registration role can gain elevated permissions they should not have, potentially compromising the application's access controls.

MitigationUpgrade the Drupal Registration module to version 2.0.1 or later to patch the incorrect privilege assignment. Review and audit user role assignments after the upgrade.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Registration RoleDrupal extension
Affected:< 2.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Drupal Registration module is installed
    Navigate to the Drupal admin dashboard and check Extend (admin/modules) for the Registration module, or use Drush: `drush pm-list --type=module | grep registration`
    Affected if The Registration module is listed as installed
  2. Identify the Registration Role module version
    Check the module's info.yml file at modules/registration_role/registration_role.info.yml, or run: `drush pm:security-jira-check --format=table` or inspect the composer.json for the registration_role package version
    Affected if The installed version is below 2.0.1 (e.g., 2.0.0, 1.x.x)
  3. Verify if the Registration role exists in the system
    Go to People > Roles (admin/people/roles) in Drupal admin, or query the role table: `SELECT * FROM role WHERE name = 'registration';`
    Affected if A role named 'Registration' or 'registration' exists in the Drupal installation
  4. Check which users are assigned the Registration role
    Go to People (admin/people) and filter by the Registration role, or query: `SELECT ur.uid, ur.rid, u.name FROM users_roles ur JOIN users u ON ur.uid = u.uid WHERE ur.rid = (SELECT rid FROM role WHERE name = 'registration');`
    Affected if Any user accounts are assigned the Registration role
  5. Audit permissions granted to the Registration role
    Navigate to People > Roles > Edit permissions for Registration role (admin/people/permissions/registration), or inspect the role_permission table: `SELECT * FROM role_permission WHERE rid = (SELECT rid FROM role WHERE name = 'registration');`
    Affected if The Registration role has elevated or administrative permissions beyond basic registration privileges

Your environment is affected if the Drupal Registration Role module version is below 2.0.1 and any user accounts are assigned the Registration role with elevated permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.1 or later
Fixed in 2.0.1
Interim mitigation

Upgrade the Drupal Registration module to version 2.0.1 or later to patch the incorrect privilege assignment. Review and audit user role assignments after the upgrade.

Recommended fix High confidence

Registration Role module version 2.0.1

  1. 1. Backup your Drupal site database and files before making any changes
  2. 2. Navigate to your Drupal site's admin panel or access the server via SSH/FTP
  3. 3. If using Composer for dependency management, run: composer update drupal/registration_role --with-all-dependencies
  4. 4. Alternatively, download the Registration Role module version 2.0.1 from www.drupal.org/project/registration_role
  5. 5. Upload the new module files to your modules directory, replacing the old version
  6. 6. Clear Drupal cache by running: drush cache-clear all or via admin UI at /admin/config/development/performance
  7. 7. Verify the module is updated to version 2.0.1 in the Drupal admin at /admin/modules
  8. 8. Test that user role permissions are functioning correctly after the update
Caveat No breaking changes documented for this security update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Registration Role Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13251 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13251 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data