# CVE-2025-34121: Idera Up.Time ≤ 7.2 post2file.php Arbitrary File Upload RCE

> Unauthenticated attackers can upload malicious PHP files to the webroot, leading to remote code execution on the monitoring server.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2025
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-7x48-359h-28rm

## What is CVE-2025-34121?

CVE-2025-34121 is a critical vulnerability in Idera Up.Time Monitoring Station, published on 16 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated arbitrary file upload vulnerability exists in Idera Up.Time Monitoring Station versions up to and including 7.2. The `wizards/post2file.php` script accepts arbitrary POST parameters, allowing attackers to upload crafted PHP files to the webroot. Successful exploitation results in remote code execution as the web server user. NOTE: The bypass for this vulnerability is tracked as CVE-2015-9263.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2025-34121 being exploited?

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

Public exploit code:

- Idera Up.Time Monitoring Station 7.0 post2file.php Arbitrary File Upload (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-34121 is a critical vulnerability in Idera Up.Time Monitoring Station, published on 16 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34121 exists.

Affected product: Idera Up.Time Monitoring Station. 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-34121/ (Markdown: https://insights.sbomify.com/CVE-2025-34121/index.md)
```

## Sources

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

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