# CVE-2025-15546: Iptanus File Upload < 5.1.7 - File Overwrite via Race Condition

> An authenticated attacker can overwrite other users' files via a race condition in the Iptanus File Upload WordPress plugin when duplicate policy is set to maintain both.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jun 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-xwgf-8969-9fm2

## What is CVE-2025-15546?

CVE-2025-15546 is a medium-severity vulnerability in Unknown Iptanus File Upload, published on 14 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Iptanus File Upload WordPress plugin before 5.1.7 does not implement proper file handling when the duplicatepolicy setting is configured to "maintain both." Due to a Time-of-Check to Time-of-Use (TOCTOU) race condition between the file existence check and the actual file write operation, an authenticated attacker can overwrite files uploaded by other users.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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


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

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

## Is CVE-2025-15546 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15546 is a medium-severity vulnerability in Unknown Iptanus File Upload, published on 14 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15546 exists.

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

## Sources

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

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