# CVE-2025-3734: Stage File Proxy - Moderately critical - Denial of Service - SA-CONTRIB-2025-035

> Attackers can cause denial of service in Drupal sites using Stage File Proxy by exploiting resource allocation flaws.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2025
- **Updated:** 16 Apr 2025
- **Also known as:** DRUPAL-CONTRIB-2025-035, GHSA-6p94-34xm-5x7f

## What is CVE-2025-3734?

CVE-2025-3734 is a medium-severity denial of service vulnerability in Drupal Stage File Proxy, published on 16 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Allocation of Resources Without Limits or Throttling vulnerability in Drupal Stage File Proxy allows Flooding.This issue affects Stage File Proxy: from 0.0.0 before 3.1.5.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2025-3734?

It affects 1 product.


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

Products: Stage File Proxy Project Stage File Proxy.

## How do I fix CVE-2025-3734?

Upgrade to a fixed version.

## Is CVE-2025-3734 being exploited?

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

## Other vulnerabilities in Drupal Stage File Proxy

- [CVE-2013-4139](https://insights.sbomify.com/CVE-2013-4139/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3734 and fix it if it is affected.

What it is: CVE-2025-3734 is a medium-severity denial of service vulnerability in Drupal Stage File Proxy, published on 16 Apr 2025. 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-2025-3734 in the wild and no public exploit code.

Affected product: Drupal Stage File Proxy. 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-2025-3734/ (Markdown: https://insights.sbomify.com/CVE-2025-3734/index.md)
```

## Sources

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

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