CVE-2025-0923VulnerabilityPublished 11 Jun 2025Updated 24 Aug 2025

CVE-2025-0923: IBM Cognos Analytics · Inclusion of Sensitive Information in Source Code

Affects IBM Cognos AnalyticsSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBM Cognos Analytics	Affected =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 =12.0.4	Fixed in–

AI-suggested

European organizations should prioritize the following specific mitigation steps: 1) Immediately review and restrict access controls on the web server hosting IBM Cognos Analytics to ensure that source code files are not publicly accessible or exposed to unauthorized users. 2) Implement web server configuration hardening to prevent directory listing and unauthorized file access, including disabling access to source code directories or files. 3) Monitor web server logs for unusual access patterns that might indicate attempts to retrieve source code or sensitive files. 4) Engage with IBM support or security advisories to obtain patches or official guidance as soon as they become available and apply them promptly. 5) Conduct a thorough security audit of the Cognos Analytics deployment to identify any other potential information leakage or misconfigurations. 6) Employ network segmentation to isolate the Cognos Analytics server from less trusted networks and limit exposure. 7) Educate administrators and developers on secure coding and deployment practices to avoid embedding sensitive information in source code or configuration files accessible via the web server. These targeted actions go beyond generic advice by focusing on access control, monitoring, and vendor engagement specific to this vulnerability.

Description

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.

Impact

For European organizations using IBM Cognos Analytics, this vulnerability poses a risk primarily to the confidentiality of sensitive business intelligence data and internal application logic. Cognos Analytics is widely used in sectors such as finance, manufacturing, healthcare, and government, where sensitive data is processed and analyzed. Exposure of source code could allow attackers to identify weaknesses or hardcoded credentials, leading to unauthorized access or data breaches. Given the remote and unauthenticated nature of the vulnerability, attackers could exploit it without needing prior access or user interaction, increasing the threat level. This could result in loss of competitive advantage, regulatory non-compliance (e.g., GDPR violations due to data exposure), and reputational damage. The impact is heightened in environments where Cognos Analytics is integrated with other critical systems or where sensitive personal or financial data is processed. However, since the vulnerability does not affect integrity or availability directly, the immediate operational disruption risk is lower, but the confidentiality breach risk remains significant.

CWE-540Inclusion of Sensitive Information in Source Code (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.
Architecture and Design · System Configuration
Recommendations include removing this script from the web server and moving it to a location not accessible from the Internet.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7234674 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Aug 2025, 00:37 UTC

WeaknessesCWE-540

Technical details

References

Community reviews

Related threats