dbcve.org
Cognos AnalyticsApplication · Ibm

CVE-2025-0923

MEDIUM · 5.3 CVSS v3.1 Published 2025-06-11
Fix available
A fix is available. Upgrade to after 12.0.4 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Cognos Analytics 11.2.0, 11.2.1, 11.2.2, 11.2.3, 11.2.4, 12.0.0, 12.0.1, 12.0.2, 12.0.3, and 12.0.4 stores source code on the web server that could aid in further attacks against the system.

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 confidence

IBM Cognos Analytics stores source code on the web server that is accessible to attackers. This information disclosure vulnerability exposes the application's internal source code, which could reveal implementation details, credentials, or other vulnerabilities that aid in further attacks against the system.

MitigationRemove or restrict access to any source code files accessible via the web server, and apply the vendor patch when available. Review web server configuration to ensure source code and internal application files are not exposed in web-accessible directories.

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
Cognos AnalyticsApplication
Affected:>= 11.2.0, <= 11.2.4>= 12.0.0, <= 12.0.4= 11.2.4

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 IBM Cognos Analytics installed version
    Check the product version through the Cognos Analytics admin console, installation directory, or by querying the Cognos Configuration. Look for a version number in the format 11.x.x or 12.x.x.
    Affected if The installed version falls within 11.2.0 through 11.2.4, or 12.0.0 through 12.0.4, including version 11.2.4 specifically.
  2. Locate web server document root directories
    Identify directories served by the web server in the Cognos Analytics installation. Check IIS, Apache, or embedded web server configurations to determine web-accessible paths.
    Affected if Source code files exist within or below any web server document root or virtual directory.
  3. Search for source code file extensions in web-accessible paths
    Use file system search or directory listing to look for files with extensions such as .java, .js, .ts, .cs, .php, .py, .rb, .jsp, .asp, .cshtml, or .vue in web-accessible directories.
    Affected if Any source code files with the above extensions are found in directories served by the web server.
  4. Check for source map files and debug files
    Look for .map files, .min.js files, source maps referenced in JavaScript files, or any .debug configuration files that may expose minified or original source code.
    Affected if Source map files or debug versions of application files are accessible via the web server.
  5. Test for exposed configuration and backup files
    Attempt to access common configuration file paths via HTTP such as backup files (.bak, .old, .zip), configuration files (web.config, .env, config.json), or git/svn metadata directories (.git, .svn).
    Affected if Configuration files, backup files, or version control metadata are accessible through web requests.

Your environment is affected if IBM Cognos Analytics version 11.2.0-11.2.4 or 12.0.0-12.0.4 is installed AND source code or configuration files are accessible via the web server in any web-accessible directory.

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.

From vendor data
Upgrade available Upgrade to a release after 12.0.4
Interim mitigation

Remove or restrict access to any source code files accessible via the web server, and apply the vendor patch when available. Review web server configuration to ensure source code and internal application files are not exposed in web-accessible directories.

Fix this in Cognos Analytics Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0923 — 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-0923 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