# CVE-2026-5624: ProjectSend upload.php cross-site request forgery

> Attackers can perform cross-site request forgery via upload.php to modify data, requiring an upgrade to ProjectSend r2029.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-8x9f-c335-83wq

## What is CVE-2026-5624?

CVE-2026-5624 is a medium-severity vulnerability in ProjectSend, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A security flaw has been discovered in ProjectSend r2002. This vulnerability affects unknown code of the file upload.php. Performing a manipulation results in cross-site request forgery. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version r2029 is able to resolve this issue. The patch is named 2c0d25824ab571b6c219ac1a188ad9350149661b. You should upgrade the affected component.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-5624 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5624 is a medium-severity vulnerability in ProjectSend, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-5624 in the wild and no public exploit code.

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

## Sources

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

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