IBM Maximo Asset Management 7.6 could allow an authenticated user perform actions they are not authorized to by modifying request parameter…

published 2020-04-17 6y ago modified 2026-06-17 4mo ago also EUVD-2019-14053

cvss: 5.4; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits: 0; none known

IBM Maximo Asset Management 7.6 could allow an authenticated user perform actions they are not authorized to by modifying request parameters. IBM X-Force ID: 163490.

Patch / fix

links 1

ibm.com/support/pages/node/6190215 advisory

Is CVE-2019-4446 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
CNA	3.0	5.4	CVSS:3.0/UI:N/AV:N/PR:L/A:N/I:L/S:U/C:L/AC:L/RC:C/E:U/RL:O
NVD	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
CNA	3.0	5.4	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
NVD	2.0	5.5	AV:N/AC:L/Au:S/C:P/I:P/A:N

Affected products

IBM Maximo Asset Management

References

ibm.com /support/pages/node/6190215
patch, vendor-advisory
exchange.xforce.ibmcloud.com /vulnerabilities/163490
vdb-entry, vendor-advisory

Sources

CVE List CVE-2019-4446
NVD CVE-2019-4446

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.