dbcve.org
File Access FixDrupal extension · Geeks4change

CVE-2026-3525

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to 8.x-1.2 or later.
See remediation →
62/100
Remediation priority · Elevated
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 File Access Fix (deprecated) allows Forceful Browsing.This issue affects File Access Fix (deprecated): from 0.0.0 before 1.2.0.

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 Drupal File Access Fix (deprecated) module versions prior to 1.2.0 contain an incorrect authorization vulnerability allowing forceful browsing, where authenticated or unauthenticated users can bypass access controls and access files they should not be permitted to reach by directly navigating to file URLs.

MitigationUpgrade to version 1.2.0 or later; if no patched version is available for this deprecated module, uninstall the module entirely and implement an alternative file access control solution using maintained Drupal modules.

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
File Access FixDrupal extension
Affected:< 8.x-1.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Locate the File Access Fix module
    Check your Drupal installation for the presence of the Geeks4change File Access Fix module in your modules directory (typically /modules, /sites/all/modules, or /modules/contrib). Look for a directory named corresponding to this module.
    Affected if The module directory exists in your modules folder
  2. Check if the module is enabled
    Query your Drupal database or use Drush command 'drush pm-list --status=enabled' to determine if the File Access Fix module is currently enabled on your site.
    Affected if The module is listed as enabled in your Drupal installation
  3. Determine the installed version
    Open the .info.yml file inside the module directory and read the 'version' or 'core' and 'version' fields to identify the exact version number installed.
    Affected if The version number is less than 8.x-1.2 (for example, 8.x-1.1, 8.x-1.0, or any version starting with 8.x-1.x that is not 1.2 or higher)
  4. Verify the module handles file access
    Review the module's routing YAML file (usually module_name.routing.yml) and any access-related PHP files in the module src/Controller or src/Plugin directories to confirm the module implements file access control logic.
    Affected if The module implements file access control and is enabled with a vulnerable version

Your environment is affected if the Geeks4change File Access Fix module is installed, enabled, and running any version prior to 8.x-1.2, allowing unauthorized file access through direct URL navigation.

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

Upgrade to version 1.2.0 or later; if no patched version is available for this deprecated module, uninstall the module entirely and implement an alternative file access control solution using maintained Drupal modules.

Recommended fix Moderate confidence

8.x-1.2 or higher

  1. Upgrade the File Access Fix module to version 1.2.0 or higher
  2. After upgrading, clear the Drupal cache to ensure the new version is properly loaded
  3. Verify that file access controls are functioning correctly after the upgrade
Caveat The File Access Fix module is deprecated; consider migrating to a supported alternative for long-term security support

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

Fix this in File Access Fix Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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