LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25480: ARMBot Unrestricted File Upload via upload.php

ARMBot contains an unrestricted file upload vulnerability in upload.php that allows unauthenticated attackers to upload arbitrary files by manipulating the file parameter with path traversal sequences. Attackers can upload PHP files with traversal payloads ../public_html/ to write executable code to the web root and achieve remote code execution.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

ARMBot has a file upload flaw that can let an unauthenticated internet attacker place files where the web server may execute them. If ARMBot is exposed, this could become remote code execution and compromise the host. Public exploit material exists, but the provided sources do not show confirmed active exploitation.

Executive priority

Prioritize exposed ARMBot systems because unauthenticated remote code execution is a high-impact risk. Treat internet-facing instances as urgent until access is restricted or vendor remediation is confirmed.

Technical view

CVE-2019-25480 affects ARMBot upload.php. The reported issue is unrestricted file upload combined with path traversal in the file parameter, allowing arbitrary files to be written into web-accessible locations. The CVSS 4.0 score is 8.7. The source bundle maps this primarily to CWE-22 and describes potential PHP execution from the web root.

Likely exposure

Highest risk is internet-facing ARMBot deployments with upload.php reachable without authentication. Exposure is unclear for specific versions because the provided affected-version data is not granular and includes conflicting default-status information.

Exploitation context

ExploitDB is listed as a public exploit reference, and VulnCheck has an advisory. The CVE is not marked KEV in the provided data, and no cited source confirms active exploitation in the wild.

Researcher notes

The provided record lacks a named patch and precise affected-version boundaries. It also lists ARMBot with wildcard versions while showing defaultStatus as unaffected, so exposure confirmation requires local asset and vendor validation.

Mitigation direction

  • Inventory ARMBot deployments and determine whether upload.php is externally reachable.
  • Check ARMBot or maintainer guidance for an official fix or replacement.
  • Restrict external access to upload.php where business use permits.
  • Require authentication and authorization for any file upload function.
  • Block executable file types from upload paths.
  • Disable server-side script execution in upload or web-writable directories.

Validation and detection

  • Confirm whether ARMBot is deployed and internet-facing.
  • Verify upload.php cannot be accessed anonymously.
  • Review web roots and upload directories for unexpected executable files.
  • Review access logs for suspicious upload requests or traversal patterns.
  • Validate web server controls prevent script execution in writable directories.
Prepared
Confidence
medium
Sources
4

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-22: 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.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

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.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-25480 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
0Timeline events
0ADP providers
3Source links

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.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2019-25480Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ARMBotARMBot*unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.