dbcve.org
TwilioDrupal extension · Twilio Project

CVE-2014-9023

MEDIUM · 5.5 CVSS v2.0 Published 2014-11-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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
The Twilio module 7.x-1.x before 7.x-1.9 for Drupal does not properly restrict access to the Twilio administration pages, which allows remote authenticated users to read and modify authentication tokens by leveraging the "access administration pages" Drupal permission.

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 Twilio module for Drupal 7.x before 1.9 fails to enforce proper access controls on its administration pages. Users with the generic 'access administration pages' permission (a common Drupal role permission) can access Twilio admin pages containing authentication tokens, allowing unauthorized reading and modification of these sensitive credentials.

MitigationUpdate Twilio module to version 7.x-1.9 or later which implements proper permission checks. Additionally, audit user roles assigned 'access administration pages' permission and restrict to only those who genuinely need admin access.

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
TwilioDrupal extension
Affected:= 7.x-1.1= 7.x-1.2= 7.x-1.4= 7.x-1.5= 7.x-1.6= 7.x-1.8= 7.x-1.9

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
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:L/Au:S/C:P/I:P/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. Identify installed Twilio module version
    Navigate to Drupal admin at Modules (admin/modules) and locate the Twilio module, or inspect the twilio.info file in sites/all/modules/contrib/twilio/ for the version line
    Affected if Twilio module version is 7.x-1.9 or earlier (7.x-1.1, 7.x-1.2, 7.x-1.4, 7.x-1.5, 7.x-1.6, 7.x-1.8)
  2. Confirm admin configuration page exists
    Locate the Twilio admin settings page path in the module (typically admin/config/media/twilio or admin/settings/twilio) and verify the menu callback is defined in twilio.module or twilio.admin.inc
    Affected if The Twilio module admin configuration page exists in the installation
  3. Check roles with access administration permission
    Go to People > Permissions (admin/user/permissions) and identify all roles granted the 'access administration pages' permission, or run 'drush role-permissions' to list role permissions
    Affected if Any role has 'access administration pages' permission besides the administrator role
  4. Verify token exposure in admin page
    As a user with only 'access administration pages' permission (not admin), navigate to the Twilio admin configuration page and observe whether Twilio authentication tokens (Account SID, Auth Token) are visible without additional Twilio-specific permission checks
    Affected if Users with only 'access administration pages' can view or modify Twilio credentials

The environment is affected if the Twilio module version is 7.x-1.9 or earlier AND any user role besides administrators has the 'access administration pages' permission, allowing unauthorized access to Twilio credentials.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Twilio module to version 7.x-1.9 or later which implements proper permission checks. Additionally, audit user roles assigned 'access administration pages' permission and restrict to only those who genuinely need admin access.

Fix this in Twilio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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