# CVE-2025-13407: GravityForms < 2.9.23.1 - Unauthenticated Arbitrary File Upload

> Unauthenticated attackers can upload PHP files via chunked upload functionality to achieve Remote Code Execution on sites using Gravity Forms.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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:** 24 Dec 2025
- **Updated:** 24 Dec 2025
- **Also known as:** GHSA-f7m4-f638-5p2j

## What is CVE-2025-13407?

CVE-2025-13407 is a medium-severity vulnerability in Unknown Gravity Forms, published on 24 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Gravity Forms WordPress plugin before 2.9.23.1 does not properly prevent users from uploading dangerous files through its chunked upload functionality, allowing attackers to upload PHP files to affected sites and achieve Remote Code Execution, granted they can discover or enumerate the upload path.

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


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

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

## Is CVE-2025-13407 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13407 exists.

Public exploit code:

- GravityForms < 2.9.23.1 - Unauthenticated Arbitrary File Upload (github_poc): https://github.com/xxconi/CVE-2025-13407

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13407 is a medium-severity vulnerability in Unknown Gravity Forms, published on 24 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13407 exists.

Affected product: Unknown Gravity Forms. 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-13407/ (Markdown: https://insights.sbomify.com/CVE-2025-13407/index.md)
```

## Sources

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

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