# CVE-2026-3525: File Access Fix (deprecated) - Moderately critical - Access bypass - SA-CONTRIB-2026-020

> Attackers can bypass access controls to view restricted files in the deprecated Drupal File Access Fix module.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** DRUPAL-CONTRIB-2026-020, GHSA-7gvm-prwv-w6hm

## What is CVE-2026-3525?

CVE-2026-3525 is a medium-severity missing authorization vulnerability in Drupal File Access Fix (deprecated), published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-3525?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/file_access_fix` | Packagist:https://packages.drupal.org/8 | All versions | 1.2.0 |

Products: Geeks4change File Access Fix.

## How do I fix CVE-2026-3525?

Upgrade to a fixed version.

## Is CVE-2026-3525 being exploited?

There is no known exploitation of CVE-2026-3525 in the wild and no public exploit code.

## Other vulnerabilities in Drupal File Access Fix (deprecated)

- [CVE-2026-3526](https://insights.sbomify.com/CVE-2026-3526/): File Access Fix (deprecated) - Moderately critical - Access bypass - SA-CONTRIB-2026-021 (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3525 and fix it if it is affected.

What it is: CVE-2026-3525 is a medium-severity missing authorization vulnerability in Drupal File Access Fix (deprecated), published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3525 in the wild and no public exploit code.

Affected product: Drupal File Access Fix (deprecated). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3525/ (Markdown: https://insights.sbomify.com/CVE-2026-3525/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3525
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3525
- OSV: https://osv.dev/vulnerability/CVE-2026-3525

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3525/
Summaries are generated and may contain mistakes; the official description above is the record.