How severe is CVE-2019-4530?

CVE-2019-4530 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2019-4530 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-4530?

CVE-2019-4530 primarily affects Ibm Maximo Asset Management. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2019-4530?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2019-4530 published?

CVE-2019-4530 was published on 2019-11-20 and last updated on 2026-06-17.

CVE-2019-4530

CVE-2019-4530 is a medium-severity vulnerability in Ibm Maximo Asset Management with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 6.5)
CVSS v2: 5.5
EPSS exploit prediction: 1% (50th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Ibm Maximo Asset Management
Published: 2019-11-20
Last modified: 2026-06-17

Description

IBM Maximo Asset Management 7.6, 7.6.1, and 7.6.1.1 could allow an authenticated user to delete a record that they should not normally be able to. IBM X-Force ID: 165586.

Frequently asked questions

What is CVE-2019-4530?: IBM Maximo Asset Management 7.6, 7.6.1, and 7.6.1.1 could allow an authenticated user to delete a record that they should not normally be able to. IBM X-Force ID: 165586.
How severe is CVE-2019-4530?: CVE-2019-4530 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2019-4530 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-4530?: CVE-2019-4530 primarily affects Ibm Maximo Asset Management. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-4530?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-4530 published?: CVE-2019-4530 was published on 2019-11-20 and last updated on 2026-06-17.

References

Affected products (3)

cpe:2.3:a:ibm:maximo_asset_management:7.6.0.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:maximo_asset_management:7.6.1:*:*:*:*:*:*:*
cpe:2.3:a:ibm:maximo_asset_management:7.6.1.1:*:*:*:*:*:*:*

More vulnerabilities in Ibm Maximo Asset Management

CVE-2021-20509 — Critical (CVSS 9.8): IBM Maximo Asset Management 7.6.0 and 7.6.1 is potentially vulnerable to CSV Injection. A remote attacker could execute…
CVE-2020-4493 — Critical (CVSS 9.8): IBM Maximo Asset Management 7.6.0 and 7.6.1 could allow an attacker to bypass authentication and issue commands using a…
CVE-2013-3323 — Critical (CVSS 9.8): A Privilege Escalation Vulnerability exists in IBM Maximo Asset Management 7.5, 7.1, and 6.2, when WebSeal with Basic…
CVE-2017-1175 — Critical (CVSS 9.8): IBM Maximo Asset Management 7.1, 7.5, and 7.6 is vulnerable to SQL injection. A remote attacker could send…
CVE-2020-4521 — High (CVSS 8.8): IBM Maximo Asset Management 7.6.0 and 7.6.1 could allow a remote authenticated attacker to execute arbitrary code on…
CVE-2018-1524 — High (CVSS 8.8): IBM Maximo Asset Management 7.6 through 7.6.3 installs with a default administrator account that a remote intruder…

All CVEs affecting Ibm Maximo Asset Management →