LiveActive security incident?Get immediate response
CVE Record

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 th...

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.

MediumCVSS 4.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-4530 is an IBM Maximo Asset Management authorization issue. An authenticated user may be able to delete a record they should not be permitted to delete. The cited severity is medium, with limited integrity impact and no stated confidentiality or availability impact.

Executive priority

Handle as a medium-priority integrity risk for affected Maximo environments. It is not supported as an active exploitation emergency by the supplied evidence, but unauthorized deletion of asset records can disrupt operations and audit reliability.

Technical view

IBM lists Maximo Asset Management 7.6, 7.6.1, and 7.6.1.1 as affected. The CVSS 3.0 score is 4.3: network-accessible, low complexity, low privileges required, no user interaction, unchanged scope, and low integrity impact. No CWE is provided in the bundle.

Likely exposure

Exposure is most likely in organizations still running IBM Maximo Asset Management 7.6, 7.6.1, or 7.6.1.1 where authenticated users can access the application. Risk increases when many internal users, contractors, or shared accounts can perform operational record workflows.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation. The CVSS exploit maturity is marked unproven. Available evidence supports an authenticated misuse scenario causing unauthorized deletion, but does not identify public exploit code, affected endpoints, or attack procedures.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, IBM advisory reference, and X-Force ID 165586. The bundle does not include a CWE, vulnerable component details, exact fixed build, or exploit indicators. Keep validation focused on version exposure and authorization behavior.

Mitigation direction

  • Inventory IBM Maximo Asset Management instances and confirm exact versions.
  • Review IBM advisory node 1108503 and X-Force ID 165586.
  • Apply IBM-recommended fixes or upgrades for affected 7.6.x deployments.
  • Restrict Maximo access to necessary authenticated users only.
  • Review roles and permissions for record deletion privileges.
  • Ensure backups and audit logging cover business-critical Maximo records.

Validation and detection

  • Confirm whether any instance runs Maximo 7.6, 7.6.1, or 7.6.1.1.
  • Check IBM advisory guidance against installed fix packs or patches.
  • Review audit logs for unexpected record deletions by low-privileged users.
  • Test authorization rules in a non-production environment only.
  • Verify deletion workflows align with intended role permissions.
Prepared
Confidence
high
Sources
4

Public sources used

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.

cve · low confidence lookup

CVE-2019-4530 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
Medium
CVSS
4.3 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/C:N/PR:L/S:U/UI:N/AC:L/A:N/AV:N/I:L/RL:O/RC:C/E:U

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
4.3CVSS 3.0MediumCVSS:3.0/C:N/PR:L/S:U/UI:N/AC:L/A:N/AV:N/I:L/RL:O/RC:C/E:U2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

4.3Medium
CVSS 3.0 vector shape for CVE-2019-4530Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/C:N/PR:L/S:U/UI:N/AC:L/A:N/AV:N/I:L/RL:O/RC:C/E:U

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMMaximo Asset Management7.6, 7.6.1, 7.6.1.1Listed
Weakness

CWE details

No CWE listed

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