CVE-2025-2986
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM Maximo Asset Management 7.6.1.3 is vulnerable to stored cross-site scripting. This vulnerability allows a privileged user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIBM Maximo Asset Management 7.6.1.3 contains a stored cross-site scripting vulnerability where a privileged user can inject arbitrary JavaScript code into the Web UI. This malicious script is stored on the server and executes when other users access the affected interface, potentially exposing credentials or session data within a trusted session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.6.1.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Maximo Asset Management installationCheck for the Maximo installation directory (commonly in /opt/ibm/maximo or C:\ibm\maximo on Windows). Look for the maximo.ear file or the psdi folder structure. Also check for running processes named 'maximo' or 'WebSphere' if Maximo runs on WebSphere.Affected if IBM Maximo Asset Management software is found on the system
-
Determine the exact Maximo versionLocate the version file or manifest. Common paths: <maximo_home>/maximo.properties, <maximo_home>/application.properties, or check the About information in the Maximo UI Administration tab. Look for a version string containing '7.6.1.3'.Affected if The installed version is exactly 7.6.1.3
-
Verify Web UI component is enabledCheck if the Maximo Web UI (maximo-ui.war or the webui ear) is deployed and the HTTP/HTTPS port for the Maximo application is accessible. Look in the WebSphere or similar application server console for deployed web applications.Affected if The Maximo Web UI interface is accessible and users can log in
-
Check for suspicious scripts in Web UI fieldsReview server-side logs (maximo.log, systemout.log) for patterns like '<script', 'javascript:', or 'onerror=' in user input fields. Inspect database tables like LONGTEXT or DOCLINKS where user content may be stored, looking for XSS payloads.Affected if Malicious JavaScript payloads are found in logs, databases, or user-submitted content that gets rendered in the UI
You are affected only if IBM Maximo Asset Management version 7.6.1.3 is installed AND the Web UI is accessible to users who could potentially inject stored XSS payloads.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement robust input validation and output encoding for all user-supplied data in the Web UI. Sanitize or escape special characters before rendering. Apply vendor-supplied security patches when available.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2986 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2986 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data