LiveActive security incident?Get immediate response
CVE Record

CVE-2019-4288: IBM Maximo Anywhere 7.6.2.0, 7.6.2.1, 7.6.3.0, and 7.6.3.1 could disclose highly senstiive user information...

IBM Maximo Anywhere 7.6.2.0, 7.6.2.1, 7.6.3.0, and 7.6.3.1 could disclose highly senstiive user information to an authenticated user with physical access to the device. IBM X-Force ID: 160631.

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

Security readout for executives and security teams

Plain-English summary

IBM Maximo Anywhere versions 7.6.2.0, 7.6.2.1, 7.6.3.0, and 7.6.3.1 could expose highly sensitive user information to an authenticated person with physical access to the device. This is not a remote internet exploit in the provided sources, but it matters where shared, lost, or weakly controlled devices are used.

Executive priority

Handle through normal vulnerability management, with higher priority for environments using shared field devices or handling regulated data. The business risk is confidentiality exposure, not service disruption or remote takeover based on provided evidence.

Technical view

The CVSS 3.0 score is 4.3 with physical attack vector, low privileges, low complexity, no user interaction, high confidentiality impact, and no integrity or availability impact. The issue is tracked as IBM X-Force ID 160631. No CWE is listed in the supplied CVE data.

Likely exposure

Exposure is most likely in organizations running the listed Maximo Anywhere versions on mobile or field devices where an authenticated user can physically access a device storing sensitive user information.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The attack context is constrained: the person must be authenticated and have physical access to the affected device.

Researcher notes

Evidence is limited to the CVE record, IBM support reference, and IBM X-Force entry. The CVSS vector indicates confidentiality-only impact requiring physical access and low privileges. Do not assume remote exploitability, broader IBM products, or specific fixed versions from the supplied data alone.

Mitigation direction

  • Inventory IBM Maximo Anywhere deployments and identify the listed affected versions.
  • Review IBM advisory 6202708 and apply IBM-provided remediation guidance.
  • Restrict physical access to managed Maximo Anywhere devices.
  • Use device lock, MDM controls, and account offboarding for shared or field devices.
  • Treat lost or unmanaged affected devices as potential confidentiality incidents.

Validation and detection

  • Confirm whether any devices run Maximo Anywhere 7.6.2.0 through 7.6.3.1.
  • Check IBM guidance for the fixed or supported remediation state.
  • Verify only authorized users can unlock and access managed devices.
  • Review MDM posture for encryption, screen lock, and remote wipe coverage.
  • Document any affected device population and remediation status.
Prepared
Confidence
medium
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-4288 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:H/AV:P/PR:L/S:U/AC:L/UI:N/A:N/I: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/C:H/AV:P/PR:L/S:U/AC:L/UI:N/A:N/I:N/RC:C/RL:O/E:U0.73.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

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

Vector: CVSS:3.0/C:H/AV:P/PR:L/S:U/AC:L/UI:N/A:N/I: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 Anywhere7.6.2.0, 7.6.2.1, 7.6.3.0, 7.6.3.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.