Cyber Resilience

CVE-2024-45077

Ibm Maximo Asset Management 7.6.1.3

Published
24 January 2025
Modified
14 August 2025
Patch / advisory
View advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0034 26th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2024-45077 is a medium-severity PHP Remote File Inclusion (CWE-98) vulnerability in Ibm Maximo Asset Management. Its CVSS base score is 6.5 (Medium).

Operationally, ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

IBM Maximo Asset Management 7.6.1.3 MXAPIASSET API is vulnerable to unrestricted file upload which allows authenticated low privileged user to upload restricted file types with a simple method of adding a dot to the end of the file name if…

more

Maximo is installed on Windows operating system.

CWE(s)
CWE-98

Related Threats

CVEs Like This One

CVE-2024-45652Same product: Ibm Maximo Asset Management
CVE-2025-2986Same product: Ibm Maximo Asset Management
CVE-2025-2987Same product: Ibm Maximo Asset Management
CVE-2023-27864Same product: Ibm Maximo Asset Management
CVE-2023-27860Same product: Ibm Maximo Asset Management
CVE-2024-45088Same product: Ibm Maximo Asset Management
CVE-2023-32333Same product: Ibm Maximo Asset Management
CVE-2023-47718Same product: Ibm Maximo Asset Management
CVE-2023-32332Same product: Ibm Maximo Asset Management
CVE-2023-32335Same product: Ibm Maximo Asset Management

Affected Assets

ibm
maximo asset management
7.6.1.3

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices such as input validation and allow-listing of include paths directly prevent the weakness.

PR.PS-01 partial match
prevents

Hardened runtime configuration (e.g., allow_url_include=off) directly blocks RFI even if code is flawed.

PR.PS-05 partial match
prevents

Execution restrictions can prevent the remote payload from running, while eliminating the weakness reduces the need for such controls.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect RFI but does not prevent the weakness by itself.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and safe include/require patterns that directly prevent remote file inclusion.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection and unsafe file operations.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce attack surface but do not specifically address dynamic file inclusion.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require whitelisting and sanitization of filenames used in include/require statements.

A.8.3 Information access restriction none match
none

Information access restriction limits what files can be read but does not address dynamic inclusion logic.

References