Infinite Automation Mango Automation 2.5.x and 2.6.x through 2.6.0 build 430 allows remote authenticated users to execute arbitrary OS comm…

published 2015-10-28 11 y ago modified 2026-06-17 4 mo ago also EUVD-2015-7799

cvss: 6.5; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 3.3%; EPSS 3.3% chance of exploitation in 30 days, percentile 88%
public exploits: 2; Exploit-DB

Infinite Automation Mango Automation 2.5.x and 2.6.x through 2.6.0 build 430 allows remote authenticated users to execute arbitrary OS commands via unspecified vectors.

Patch / fix

links 1

ics-cert.us-cert.gov/advisories/ICSA-15-300-02 advisory

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-15-300-02A updated 2025-06-09 cvss 6.3

Infinite Automation Systems Mango Automation Vulnerabilities (Update A)

Infinite Automation Systems Mango Automation >=2.5.0, <=2.6.0_beta, <2.7.0
affected: mitigation “Update to the latest version. (http://infiniteautomation.com/index.php/download)”

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Timeline

2015-09-28 First public exploit (EDB-38338)
2015-10-28 Published

Exploit prediction

3.26% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

EDB-42698 Infinite Automation Mango Automation - Command Injection (Metasploit) remote, 2017-09-13
EDB-38338 Mango Automation 2.6.0 - Multiple Vulnerabilities webapps, 2015-09-28

CVSS scores

assigned by	version	score	vector
NVD	2.0	6.5	AV:N/AC:L/Au:S/C:P/I:P/A:P

Classification

Weakness

CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

ics-cert.us-cert.gov /advisories/ICSA-15-300-02
patch, third-party-advisory, us-government-resource
exploit-db.com /exploits/42698/
exploit

Sources

CVE List CVE-2015-7901
NVD CVE-2015-7901

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary