dbcve.org
Authenticated User Page CachingDrupal extension · Drupal

CVE-2013-4226

MEDIUM · 6.5 CVSS v3.1 Published 2020-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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 Authenticated User Page Caching (Authcache) module 7.x-1.x before 7.x-1.5 for Drupal does not properly restrict access to cached pages, which allows remote attackers with the same role-combination as the superuser to obtain sensitive information via the cached pages of the superuser.

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 Authcache module for Drupal 7.x before 7.x-1.5 fails to properly isolate cached pages between users who share the same role combination. When a superuser visits a page, that page gets cached. Another authenticated user with an identical role combination can then potentially access those cached superuser pages, exposing sensitive information.

MitigationUpdate the Authcache module to version 7.x-1.5 or later. Review cached content and user role assignments to ensure no unauthorized access has occurred.

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
Authenticated User Page CachingDrupal extension
Affected:= 7.x-1.0= 7.x-1.1= 7.x-1.2= 7.x-1.3= 7.x-1.4= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 Authcache module is installed
    Check for the presence of the authcache module in your Drupal installation's modules directory (sites/all/modules/authcache or sites/all/modules/contrib/authcache) or list enabled modules via Drush: `drush pm-list --type=module --status=enabled | grep authcache`
    Affected if The Authcache module is present and enabled on the system
  2. Determine installed Authcache version
    Run `drush pm-list --type=module | grep authcache` to see the version, or check the module's .info file at sites/all/modules/authcache/authcache.info for the version line
    Affected if The installed version is 7.x-1.0, 7.x-1.1, 7.x-1.2, 7.x-1.3, 7.x-1.4, or 7.x-1.5 (all versions before 7.x-1.5)
  3. Confirm Authcache caching is actively configured
    Check the Drupal variable table for authcache settings via SQL: `SELECT * FROM variable WHERE name LIKE 'authcache%';` or inspect settings.php for authcache configuration entries. Also check if Page Caching is enabled at admin/config/development/performance
    Affected if Authcache caching is enabled and the module is actively caching pages for authenticated users
  4. Identify role assignment exposure
    Review user role assignments at admin/config/people/roles to identify which roles exist, then check user accounts (via admin/config/people or database query) to see which users share identical role combinations
    Affected if Multiple users share the same role combination AND at least one of those users is a superuser (administrator) who would have cached privileged content accessible to others with matching roles

The environment is affected if Authcache module versions 7.x-1.0 through 7.x-1.5 are installed with caching enabled, and multiple users share identical role combinations including elevated privileges.

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 the Authcache module to version 7.x-1.5 or later. Review cached content and user role assignments to ensure no unauthorized access has occurred.

Fix this in Authenticated User Page Caching Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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