dbcve.org
Rest \& Json Api AuthenticationDrupal extension · Rest \& Json Api Authentication Project

CVE-2024-13258

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 2.0.13 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Authorization vulnerability in Drupal Drupal REST & JSON API Authentication allows Forceful Browsing.This issue affects Drupal REST & JSON API Authentication: from 0.0.0 before 2.0.13.

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

An incorrect authorization vulnerability in Drupal's REST & JSON API Authentication module allows attackers to bypass access controls through forceful browsing, potentially accessing protected resources without proper authentication. This is a critical authorization bypass (CWE-863) affecting versions prior to 2.0.13.

MitigationUpgrade Drupal REST & JSON API Authentication module to version 2.0.13 or later to obtain the patched version with proper authorization checks.

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
Rest \& Json Api AuthenticationDrupal extension
Affected:< 2.0.13

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if REST & JSON API Authentication module is installed
    In Drupal admin, go to Extend page and search for 'REST & JSON API Authentication' module, or check the module directory at /modules/rest_api_authentication for Drupal installations
    Affected if The module is listed as installed or the module directory exists in the Drupal installation
  2. Determine the installed version of the module
    In Drupal admin, go to Extend page, find 'REST & JSON API Authentication' and view the version number in the module description, or check the module's .info.yml file for the version
    Affected if The displayed version is lower than 2.0.13 (e.g., 2.0.12, 2.0.11, etc.)
  3. Verify REST API endpoints are publicly accessible
    Attempt to access REST API endpoints without authentication headers (e.g., using curl -H 'Accept: application/json' https://yoursite.com/api/endpoint) or check the module's endpoint configuration at /admin/config/services/rest_api
    Affected if API requests complete successfully without returning 401/403 authentication errors
  4. Check if JSON API endpoints allow unauthorized access
    Send requests to JSON API endpoints (typically /jsonapi/ paths) without authentication credentials and observe if protected resources are returned
    Affected if JSON API responses return data that should require authentication, without 401/403 errors

If the REST & JSON API Authentication module is installed with a version lower than 2.0.13 and REST/JSON API endpoints are publicly accessible without authentication, the environment is vulnerable to this authorization bypass.

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.13 or later
Fixed in 2.0.13
Interim mitigation

Upgrade Drupal REST & JSON API Authentication module to version 2.0.13 or later to obtain the patched version with proper authorization checks.

Recommended fix High confidence

2.0.13

  1. 1. Back up your Drupal database and files before making any changes
  2. 2. Navigate to your Drupal admin panel or use Composer to update the 'REST & JSON API Authentication' module
  3. 3. Update the module to version 2.0.13 or later: `composer update drupal/rest_json_api_authentication --with-all-dependencies` or via the Drupal admin UI at /admin/modules
  4. 4. Run database updates if required: `drush updatedb` or via the admin UI at /update.php
  5. 5. Clear the Drupal cache: `drush cr` or via the admin UI at /admin/config/development/performance
  6. 6. Verify the update was successful by checking the module version at /admin/modules
Caveat Minor: Review module configuration after upgrade as default settings may have changed

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

Fix this in Rest \& Json Api Authentication Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13258 — 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-13258 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