# CVE-2014-9156: Missing authorization in n/a

> Authenticated users with content creation permissions can bypass access controls to read private files in the Drupal FileField module.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2014
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-974p-rx3f-rxv5

## What is CVE-2014-9156?

CVE-2014-9156 is a medium-severity missing authorization vulnerability in n/a, published on 1 Dec 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The FileField module 6.x-3.x before 6.x-3.13 for Drupal does not properly check permissions to view files, which allows remote authenticated users with permission to create or edit content to read private files by attaching an uploaded file.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2014-9156?

It affects 1 product.


Products: Filefield Project Filefield.

## How do I fix CVE-2014-9156?

No fix has been published for CVE-2014-9156 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-9156 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9156 and fix it if it is affected.

What it is: CVE-2014-9156 is a medium-severity missing authorization vulnerability in n/a, published on 1 Dec 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9156 in the wild and no public exploit code.

Affected product: n/a. 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-2014-9156/ (Markdown: https://insights.sbomify.com/CVE-2014-9156/index.md)
```

## Sources

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

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