dbcve.org
License Metric ToolApplication · Ibm

CVE-2025-36352

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-29
Fix available
A fix is available. Upgrade to 9.2.41 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
IBM License Metric Tool 9.2.0 through 9.2.40 is vulnerable to stored cross-site scripting. This vulnerability allows an authenticated 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 · high confidence

IBM License Metric Tool versions 9.2.0 through 9.2.40 contain a stored cross-site scripting vulnerability in the Web UI. An authenticated attacker can inject malicious JavaScript code that persists in the application, potentially allowing credential theft or session hijacking within a trusted user session.

MitigationUpgrade IBM License Metric Tool to version 9.2.41 or later to obtain the security patch. Prior to upgrade, document current configuration and validate upgrade in a non-production environment.

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
License Metric ToolApplication
Affected:< 9.2.41

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IBM License Metric Tool version
    Use the product's version reporting mechanism (such as the 'lmgrd -version' command, version information in the installation directory, or the About section in the Web UI) to determine the exact version number
    Affected if The installed version is 9.2.0 through 9.2.40 (any version below 9.2.41)
  2. Confirm Web UI component is accessible
    Verify that the Web UI interface is enabled and reachable (typically via browser access to the application's web port). Check configuration files or administration settings to confirm the UI service status
    Affected if The Web UI is enabled and accessible to users
  3. Determine if authentication is configured for the Web UI
    Review the authentication settings in the product configuration to confirm whether user login is required to access the Web UI functionality
    Affected if Users can authenticate to the Web UI (since the vulnerability requires an authenticated attacker)
  4. Inspect user-created content in the Web UI
    Review any user-accessible fields in the Web UI where data can be submitted and stored (such as custom reports, user profiles, or data import fields) for any unexpected script tags or JavaScript content
    Affected if Unfiltered script content exists in stored Web UI fields

You are affected if IBM License Metric Tool is version 9.2.40 or earlier AND the Web UI is enabled and accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 9.2.41 or later
Fixed in 9.2.41
Interim mitigation

Upgrade IBM License Metric Tool to version 9.2.41 or later to obtain the security patch. Prior to upgrade, document current configuration and validate upgrade in a non-production environment.

Recommended fix High confidence

9.2.41

  1. Back up your IBM License Metric Tool database and configuration files
  2. Download IBM License Metric Tool version 9.2.41 from IBM Fix Central or your authorized IBM distribution channel
  3. Follow IBM's standard upgrade procedure for your deployment type (standalone or clustered)
  4. After upgrade, verify the Web UI is accessible and functioning normally
  5. Log in and confirm the stored XSS vulnerability is remediated by verifying that arbitrary JavaScript in input fields is no longer executable

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in License Metric Tool Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36352 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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