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.
Security readout for executives and security teams
Plain-English summary
A remote attacker may be able to take control of an affected Idera Up.Time Monitoring Station without credentials. The vulnerable web script accepts uploaded PHP files, which can execute with the web server account’s permissions. Internet-facing systems running version 7.2 or earlier require urgent review.
Executive priority
Treat internet-accessible or otherwise untrusted-network-reachable installations as an immediate priority. Public exploit resources and unauthenticated remote code execution create credible takeover risk. Confirm exposure now, contain vulnerable interfaces, investigate for compromise, and obtain authoritative vendor remediation guidance.
Technical view
CVE-2025-34121 is an unauthenticated arbitrary file upload in wizards/post2file.php affecting Up.Time Monitoring Station through 7.2. Insufficient authentication and file validation allow server-executable content in the webroot, resulting in code execution as the web server user. The source bundle identifies CVE-2015-9263 as a related bypass.
Likely exposure
Highest risk applies to Up.Time Monitoring Station 7.2 or earlier when its web interface is internet-accessible or reachable from untrusted networks. Internally hosted systems remain exposed following network compromise. The supplied structured affected-version data is inconsistent, so confirm inventory against vendor guidance.
Exploitation context
Public exploit material is referenced in Metasploit and Exploit-DB, substantially lowering the barrier to attempted exploitation. However, the source bundle marks this CVE as absent from KEV, and the supplied sources do not establish active exploitation in the wild.
Researcher notes
The CVE description supports impact through version 7.2, but the structured affected entry lists version 0 with a default unaffected status. This inconsistency limits precise product matching. No fixed release or vendor-authored mitigation is identified in the supplied bundle. CVE-2015-9263 should be reviewed separately as the stated bypass.
Mitigation direction
Obtain current remediation and supported-version guidance from Idera before selecting an upgrade target.
Restrict the monitoring interface to trusted management networks and authenticated administrative paths.
Temporarily block external access to wizards/post2file.php if operational testing confirms this is safe.
Isolate potentially compromised systems and begin incident response before restoring service.
Apply least privilege to the web server account and restrict webroot write permissions where supported.
Validation and detection
Inventory all Up.Time Monitoring Station deployments and confirm their exact installed versions.
Determine whether wizards/post2file.php is reachable without authentication from each relevant network zone.
Review web logs for unexpected POST requests targeting wizards/post2file.php.
Inspect the webroot for unexpected or recently created PHP files.
Assess suspicious processes and files created under the web server account.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.