CVE-2005-1601

5.0 MEDIUM 1% exploit odds No fix listed

What it is

MRO Maximo Self Service 4 and 5 stores certain information under the web document root using file extensions that are not processed by Tomcat, which allows remote attackers to obtain sensitive information via a direct request for the file, such as MXServer.properties.

At a glance

Exploitability: Can be exploited over the network without logging in. Limited direct impact.
Exploit odds: 1.4% chance of exploitation in the next 30 days (EPSS).
Fix: No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

2005-05-16 04:00 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-16 22:13 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 1.4% in the next 30 days (EPSS).
Severity: 5.0 MEDIUM (CVSS).
Fix: none linked yet, which raises it.

Details

Published: 2005-05-16 04:00 UTC
Last modified: 2026-06-16 22:13 UTC
Exploit probability: 1.4% · EPSS, next 30 days
Record status: Modified

Affected

Mro Software Maximo Self Service 4.0
Mro Software Maximo Self Service 5.0

Attack profile CVSS 2.0 · 5.0

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: Partial
Integrity: None
Availability: None

Raw vector

AV:N/AC:L/Au:N/C:P/I:N/A:N

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2005-1601.md and follow it. Check whether this project is affected by CVE-2005-1601. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

References

NVD record · CVE.org record