Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2016-6072

IBM Maximo Asset Management is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in…

Medium5.4EPSS 0.54%
Published
Updated
Reserved
Assigned by
ibm

Description

IBM Maximo Asset Management is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

Timeline

  1. ID reserved

    By ibm

  2. · 7 months later

    Published

  3. · 8 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2016-6072, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.0Medium5.4CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS (exploitation in 30 days)
0.54% · top 54% of all CVEs (8 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.4.

Weakness

Affected products

  • IBM Corporation · Maximo Asset Management

    • affected 6.2
    • affected 7.1
    • affected 7.5
    • affected 7.5.0.0
    • affected 7.5.0.10
    • affected 7.1.0.0
    • affected 6.2.0.0
    • affected 7.2
    • affected 7.1.1
    • affected 7.1.2
    • affected 7.2.1
    • affected 6.2.1
    • affected 6.2.2
    • affected 6.2.3
    • affected 6.2.4
    • affected 6.2.5
    • affected 6.2.6
    • affected 6.2.7
    • affected 6.2.8
    • affected 7.1.1.1
    • affected 7.1.1.10
    • affected 7.1.1.11
    • affected 7.1.1.12
    • affected 7.1.1.2
    • affected 7.1.1.5
    • affected 7.1.1.6
    • affected 7.1.1.7
    • affected 7.1.1.8
    • affected 7.1.1.9
    • affected 7.5.0.1
    • affected 7.5.0.2
    • affected 7.5.0.3
    • affected 7.5.0.4
    • affected 7.5.0.5
    • affected 7.6
    • affected 7.5.0
    • affected 7.6.0

References (2)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2016-6072 badge
[![CVE-2016-6072](https://cveledger.app/badge/CVE-2016-6072.svg)](https://cveledger.app/cve/CVE-2016-6072)

Record last updated .