CVE-2025-27368VulnerabilityPublished 12 Nov 2025

CVE-2025-27368: IBM OpenPages · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects IBM OpenPagesSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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 12 Nov 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 OpenPages	Affected =9.0 =9.1	Fixed in–

AI-suggested

To mitigate CVE-2025-27368, European organizations should implement the following specific measures: 1) Review and tighten user access controls within IBM OpenPages to ensure least privilege principles are enforced, limiting authenticated users to only necessary data and functions. 2) Monitor and audit REST API endpoint access logs to detect unusual or unauthorized queries that may indicate exploitation attempts. 3) Employ network segmentation and firewall rules to restrict access to OpenPages management interfaces to trusted administrative networks only. 4) Engage with IBM support to obtain any available patches or security advisories and apply updates promptly once released. 5) Conduct internal penetration testing focused on REST API endpoints to identify and remediate similar exposure risks. 6) Educate administrators and users about the risks of credential compromise and enforce strong authentication mechanisms such as multi-factor authentication. 7) Consider deploying Web Application Firewalls (WAF) with custom rules to detect and block suspicious REST API calls targeting metadata endpoints. These targeted actions go beyond generic advice by focusing on access control, monitoring, and proactive testing specific to the vulnerability's nature.

Description

IBM OpenPages 9.0 and 9.1 is vulnerable to information disclosure of sensitive information due to a weaker than expected security for certain REST end points used by the user interface of OpenPages. An authenticated user is able to obtain certain information about system metadata for areas beyond what the user is intended to view.

Impact

For European organizations, the primary impact of CVE-2025-27368 is the unauthorized disclosure of sensitive system metadata within IBM OpenPages environments. This can lead to increased risk of targeted attacks by revealing internal system configurations or security posture details. Organizations in regulated sectors such as finance, healthcare, and government may face compliance risks if sensitive information is exposed beyond authorized personnel. Although the vulnerability does not allow data modification or service disruption, the confidentiality breach could facilitate lateral movement or privilege escalation attempts by malicious insiders or compromised accounts. The impact is heightened in large enterprises relying heavily on OpenPages for risk and compliance management, where sensitive governance data is stored. Since exploitation requires authentication, the risk is limited to insiders or attackers who have obtained valid credentials, but the ease of access to unauthorized metadata still represents a significant security concern. Overall, the vulnerability could undermine trust in the integrity of governance systems and complicate regulatory compliance efforts in Europe.

Summary

CVE-2025-27368 is an information disclosure vulnerability classified under CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere) affecting IBM OpenPages versions 9.0 and 9.1. The root cause lies in insufficient security controls on certain REST API endpoints used by the OpenPages user interface. These endpoints expose system metadata that should be restricted based on user privileges. An attacker with valid authentication credentials can exploit this weakness to retrieve sensitive system information beyond their authorized access scope. The vulnerability does not allow for modification of data or denial of service, but it compromises confidentiality by leaking potentially sensitive metadata. The CVSS v3.1 base score is 4.3 (medium), reflecting that the attack vector is network-based with low attack complexity, requiring privileges but no user interaction, and impacting confidentiality only. No known exploits have been reported in the wild, and IBM has not yet published patches or mitigations at the time of disclosure. The vulnerability affects enterprise environments where OpenPages is deployed for governance, risk, and compliance management, potentially exposing internal system details that could aid further attacks or violate regulatory requirements. The issue highlights the importance of strict access control enforcement on RESTful interfaces within enterprise applications.

CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Nov 2025, 19:59 UTC

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats