dbcve.org
Rest\/jsonDrupal extension · Rest\/json Project

CVE-2016-20006

HIGH · 7.5 CVSS v3.1 Published 2021-01-01
Fix available
A fix is available. Upgrade to after 7.x-1.5 or later.
See remediation →
84/100
Remediation priority · High
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
The REST/JSON project 7.x-1.x for Drupal allows blockage of user logins, aka SA-CONTRIB-2016-033. NOTE: This project is not covered by Drupal's security advisory policy.

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 · moderate confidence

The REST/JSON contributed module for Drupal 7.x-1.x contains a vulnerability that allows attackers to block user logins, likely due to improper authorization or access control in the login blocking functionality. This represents a denial-of-service or account takeover risk where unauthorized actors can prevent legitimate users from accessing the system.

MitigationReplace or remove the unmaintained REST/JSON module since it is not covered by Drupal's security advisory policy, and migrate to a supported REST/API solution while verifying user login functionality is unaffected.

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\/jsonDrupal extension
Affected:<= 7.x-1.5

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 module is installed
    Locate the module directory in your Drupal installation: Look for a folder named 'rest_json', 'restws', or similar REST-related module in sites/all/modules or sites/all/modules/contrib. Check your Drupal database in the 'system' table for entries where type='module' and name contains 'rest' or 'json'.
    Affected if The module folder exists and the module is listed in the Drupal system table as installed.
  2. Determine the installed module version
    Check the module's .info file (e.g., rest_json.info or restws.info) for the version line, or query the Drupal 'system' database table for the 'version' field corresponding to the REST/JSON module entry.
    Affected if The installed version is 7.x-1.5 or lower.
  3. Verify the module is enabled
    Check if the module is enabled by querying the 'system' table where type='module' and status=1, or access the Drupal administration page at admin/modules to see if the REST/JSON module is listed as enabled.
    Affected if The module shows status=1 in the database or appears as enabled in admin/modules.
  4. Inspect REST endpoint accessibility
    Test unauthenticated access to login-related endpoints exposed by the module. Use a tool like curl to send requests to endpoints such as /api/user/login or /rest/user/login without providing authentication credentials.
    Affected if Unauthenticated requests to login-related REST endpoints return successful responses or allow modification of login blocking settings without authorization.
  5. Review access logs for login blocking activity
    Examine web server access logs (Apache, Nginx) and Drupal watchdog logs for suspicious patterns: multiple requests to REST login endpoints from external IPs, or log entries indicating user login status modifications performed via API without proper admin authentication.
    Affected if Logs show unauthorized API calls modifying user login capabilities or blocking legitimate user accounts.

A Drupal 7 site is affected if the REST/JSON module version 7.x-1.5 or lower is installed and enabled, and login-related REST endpoints are exposed without proper authorization controls.

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.

From vendor data
Upgrade available Upgrade to a release after 7.x-1.5
Interim mitigation

Replace or remove the unmaintained REST/JSON module since it is not covered by Drupal's security advisory policy, and migrate to a supported REST/API solution while verifying user login functionality is unaffected.

Fix this in Rest\/json Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,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 $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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