CVE-2025-23227
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 Tivoli Application Dependency Discovery Manager 7.3.0.0 through 7.3.0.11 is vulnerable to stored cross-site scripting. This vulnerability allows authenticated users 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 confidenceIBM Tivoli Application Dependency Discovery Manager versions 7.3.0.0-7.3.0.11 contains a stored cross-site scripting vulnerability in its Web UI. Authenticated users can inject arbitrary JavaScript code into application input fields, which gets stored and executed in the browsers of other users viewing the affected content, potentially leading to session hijacking and credentials disclosure.
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.3.0.0, <= 7.3.0.11CVSS 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 the installed TADDM versionUse the product's version reporting mechanism or check the product installation directory for version metadata files. Common methods include reviewing the installation logs, using the product's CLI version command, or checking the about dialog in the Web UI.Affected if The installed version falls within the range 7.3.0.0 through 7.3.0.11 (inclusive).
-
Confirm the Web UI is accessibleVerify that the TADDM web interface is exposed and reachable. Check network configuration or attempt to access the Web UI login page.Affected if The Web UI is enabled and accessible to users or attackers on the network.
-
Verify authentication is configuredReview the TADDM authentication settings to confirm user authentication is enabled for the Web UI. Check whether local users, LDAP users, or other authentication mechanisms are active.Affected if Authentication is enabled, as the vulnerability requires an authenticated user to inject the malicious script.
-
Inspect input handling in Web UI fieldsLog into the Web UI as an authenticated user and examine application input fields (such as configuration fields, naming fields, or description fields) where user-supplied data can be stored and displayed to other users.Affected if User-supplied input in Web UI fields is not properly validated or encoded before storage and display.
A user is affected if TADDM version 7.3.0.0-7.3.0.11 is installed with the Web UI enabled and authentication configured, allowing stored XSS injection in application input fields.
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 dataApply the vendor security patch or upgrade to a fixed version. Implement robust input validation and output encoding for all user-supplied data rendered in the Web UI, and configure a Content Security Policy to mitigate XSS execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23227 — 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-23227 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