# CVE-2025-12352: Gravity Forms <= 2.9.20 - Unauthenticated Arbitrary File Upload via 'copy_post_image'

> Unauthenticated attackers can upload arbitrary files leading to remote code execution on sites with specific configuration settings enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8ff8-c7j7-c996

## What is CVE-2025-12352?

CVE-2025-12352 is a critical vulnerability in Gravity Forms, published on 7 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Gravity Forms plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the copy_post_image() function in all versions up to, and including, 2.9.20. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. This only impacts sites that have allow_url_fopen set to `On`, the post creation form enabled along with a file upload field for the post

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2025-12352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12352 is a critical vulnerability in Gravity Forms, published on 7 Nov 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-12352 in the wild and no public exploit code.

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

## Sources

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

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