dbcve.org
Restful Web ServicesDrupal extension · Restful Web Services Project

CVE-2024-13255

HIGH · 7.5 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 7.x-2.10 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
Exposure of Sensitive Information Through Data Queries vulnerability in Drupal RESTful Web Services allows Forceful Browsing.This issue affects RESTful Web Services: from 7.X-2.0 before 7.X-2.10.

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

A vulnerability in Drupal's RESTful Web Services module (versions 7.X-2.0 through 7.X-2.9) allows attackers to perform forceful browsing to access sensitive information through data queries. The issue stems from insufficient access controls on REST endpoints, potentially exposing protected data that should require authentication.

MitigationUpdate RESTful Web Services module to version 7.X-2.10 or later. If immediate patching is not possible, restrict access to REST endpoints via firewall rules or authentication requirements at the web server level.

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
Restful Web ServicesDrupal extension
Affected:>= 7.x-2.0, < 7.x-2.10

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

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

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. Verify RESTful Web Services module is installed
    In the Drupal admin interface, navigate to Modules (admin/modules) and look for 'RESTful Web Services' in the list, or check the modules directory for the restful module folder
    Affected if The module is present in the installation
  2. Determine the installed version of the RESTful Web Services module
    Check the module's .info file (typically at sites/all/modules/restful/restful.info or within the module directory) for the version line, or look at the module's listing in admin/modules where the version is displayed
    Affected if Version is 7.x-2.0 through 7.x-2.9 (anything less than 7.x-2.10)
  3. Confirm REST endpoints are exposed
    Check the module configuration at admin/config/services/rest or review the site's routing/cron.php for REST resource exposure; also check if any REST resources are enabled in the REST UI module if installed
    Affected if Any REST resources or endpoints are enabled and accessible without authentication
  4. Verify access controls on REST endpoints
    Review the permissions at admin/people/permissions for 'restful' related permissions and check endpoint configuration at admin/config/services/rest for any endpoint set to 'anonymous user' access
    Affected if REST endpoints are accessible to anonymous users or lack proper authentication requirements

You are affected if the RESTful Web Services module versions 7.x-2.0 through 7.x-2.9 are installed with exposed REST endpoints that allow unauthenticated access.

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 7.x-2.10 or later
Fixed in 7.x-2.10
Interim mitigation

Update RESTful Web Services module to version 7.X-2.10 or later. If immediate patching is not possible, restrict access to REST endpoints via firewall rules or authentication requirements at the web server level.

Recommended fix High confidence

7.x-2.10 or later

  1. 1. Back up your Drupal site database and files before making any changes
  2. 2. Update the RESTful Web Services module to version 7.x-2.10 or later using your package manager (e.g., composer require drupal/restful:^2.10 or via the Drupal admin UI)
  3. 3. Clear Drupal caches after the update (using drush cr or through admin UI at /admin/config/development/performance)
  4. 4. Test your REST endpoints to verify the vulnerability is remediated and functionality still works
Caveat Minor patch release; review module release notes for any breaking changes before upgrading

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

Fix this in Restful Web Services Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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