LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4526: IBM Maximo Asset Management 7.6.0 and 7.6.1 is vulnerable to cross-site request forgery which could allow a...

IBM Maximo Asset Management 7.6.0 and 7.6.1 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 182436.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

IBM Maximo Asset Management 7.6.0 and 7.6.1 have a CSRF flaw that could let an attacker cause unauthorized actions through a trusted user’s session. The known impact is limited to integrity, not data disclosure or service outage, but business risk depends on what affected users can change.

Executive priority

Address during normal vulnerability remediation, with faster handling for externally reachable Maximo systems or environments where trusted users can alter operational assets, work orders, inventory, or configuration data.

Technical view

CVE-2020-4526 is a cross-site request forgery issue in IBM Maximo Asset Management 7.6.0 and 7.6.1. CVSS 3.0 score is 4.3 with network attack vector, low complexity, required user interaction, no privileges required, and low integrity impact. IBM X-Force tracks it as ID 182436.

Likely exposure

Exposure is limited to organizations running IBM Maximo Asset Management 7.6.0 or 7.6.1. The source bundle does not identify other IBM Maximo products, cloud services, or later versions as affected.

Exploitation context

The provided sources do not show active exploitation. KEV is false, and the CVSS temporal vector marks exploit maturity as unproven. Treat this as a credible web application risk, not as an actively exploited emergency based on available evidence.

Researcher notes

Evidence is concise: IBM identifies affected versions and CSRF impact, while the CVSS vector defines the practical constraints. The bundle does not provide affected endpoints, proof-of-concept details, or complete fix version names, so validation should stay advisory-driven.

Mitigation direction

  • Check whether any Maximo Asset Management instance runs version 7.6.0 or 7.6.1.
  • Review IBM support guidance for CVE-2020-4526 and X-Force ID 182436.
  • Apply IBM-provided fixed releases, interim fixes, or configuration guidance where applicable.
  • Prioritize remediation for internet-accessible or high-privilege Maximo deployments.
  • Limit user privileges for accounts able to perform sensitive Maximo actions.

Validation and detection

  • Inventory Maximo Asset Management versions across production, staging, and disaster recovery environments.
  • Confirm affected installations against IBM’s advisory and X-Force vulnerability record.
  • Verify that vendor-recommended fixes or updates are installed.
  • Review sensitive workflows for CSRF protections after remediation.
  • Check access logs for unusual state-changing actions by trusted users.
Prepared
Confidence
high
Sources
4

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

Vulnerability scoring details

Base CVSS 3.0 score

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

Vector: CVSS:3.0/AC:L/A:N/AV:N/I:L/S:U/C:N/UI:R/PR:N/RC:C/RL:O/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.0, 7.6.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.