CVE-2025-69907: Newgen OmniDocs Information Disclosure

CVE-2025-69907 Overview

An unauthenticated information disclosure vulnerability exists in Newgen OmniDocs due to missing authentication and access control on the /omnidocs/GetListofCabinet API endpoint. A remote attacker can access this endpoint without valid credentials to retrieve sensitive internal configuration information, including cabinet names and database-related metadata. This allows unauthorized enumeration of backend deployment details and may facilitate further targeted attacks.

Critical Impact

Unauthenticated attackers can remotely enumerate sensitive backend configuration data including cabinet names and database metadata, potentially enabling reconnaissance for further targeted attacks against the OmniDocs deployment.

Affected Products

• Newgen OmniDocs (versions with vulnerable /omnidocs/GetListofCabinet endpoint)

Discovery Timeline

• 2026-01-23 - CVE CVE-2025-69907 published to NVD
• 2026-01-26 - Last updated in NVD database

Technical Details for CVE-2025-69907

Vulnerability Analysis

This vulnerability is classified under CWE-284 (Improper Access Control), which occurs when software does not properly restrict access to resources or functionality. In the case of Newgen OmniDocs, the /omnidocs/GetListofCabinet API endpoint lacks proper authentication and authorization mechanisms, allowing any remote attacker to query it without providing valid credentials.

The exposed endpoint returns sensitive internal configuration information that should only be accessible to authenticated and authorized users. This information includes cabinet names (which represent logical storage containers within OmniDocs) and database-related metadata that reveals details about the backend infrastructure.

Root Cause

The root cause of this vulnerability is the absence of authentication checks and access control enforcement on the /omnidocs/GetListofCabinet API endpoint. The application fails to verify whether incoming requests originate from authenticated users before processing them and returning sensitive data. This represents a fundamental security design flaw where security-sensitive functionality was deployed without appropriate access restrictions.

Attack Vector

The attack can be executed remotely over the network without requiring any authentication, user interaction, or special privileges. An attacker simply needs to send an HTTP request to the vulnerable /omnidocs/GetListofCabinet endpoint on a publicly accessible or network-reachable OmniDocs instance.

The information gathered through this vulnerability can be leveraged for further reconnaissance activities, helping attackers understand the target environment's structure, identify potential targets for data exfiltration, or craft more sophisticated attacks against other OmniDocs components. The attack surface is particularly concerning for internet-facing deployments.

For detailed technical information about this vulnerability, refer to the GitHub CVE-2025-69907 Advisory.

Detection Methods for CVE-2025-69907

Indicators of Compromise

• Unusual HTTP requests to /omnidocs/GetListofCabinet endpoint from external or unauthorized IP addresses
• High volume of API calls to cabinet enumeration endpoints from single source IPs
• Access logs showing unauthenticated requests successfully retrieving cabinet metadata
• Network traffic patterns indicating systematic enumeration of OmniDocs resources

Detection Strategies

• Implement web application firewall (WAF) rules to monitor and alert on requests to /omnidocs/GetListofCabinet from unauthenticated sessions
• Configure application-level logging to capture all access attempts to sensitive API endpoints regardless of authentication status
• Deploy network intrusion detection signatures to identify reconnaissance patterns targeting OmniDocs installations

Monitoring Recommendations

• Enable detailed access logging for all OmniDocs API endpoints and forward logs to a SIEM solution for correlation analysis
• Establish baseline traffic patterns for legitimate cabinet enumeration activity and alert on anomalies
• Monitor for repeated failed authentication attempts followed by successful unauthenticated API access, which may indicate exploitation attempts

How to Mitigate CVE-2025-69907

Immediate Actions Required

• Restrict network access to the /omnidocs/GetListofCabinet endpoint using firewall rules or reverse proxy configurations to allow only trusted sources
• Implement authentication requirements at the web server or application gateway level as an interim control
• Review access logs to determine if the vulnerability has already been exploited and identify any unauthorized data access
• Consider temporarily disabling the vulnerable endpoint if cabinet enumeration functionality is not business-critical

Patch Information

Contact Newgen Software for official security patches or updated versions that address this vulnerability. Monitor the NewGen Software Homepage and official support channels for security bulletins related to OmniDocs. Organizations should prioritize applying vendor-provided fixes as soon as they become available.

Workarounds

• Deploy a reverse proxy or WAF in front of OmniDocs to enforce authentication on the vulnerable endpoint
• Configure network segmentation to ensure OmniDocs is not directly accessible from untrusted networks
• Implement IP allowlisting at the network layer to restrict access to the OmniDocs application to authorized internal networks only

# Example: Restrict access to vulnerable endpoint using nginx
location /omnidocs/GetListofCabinet {
    # Deny all external access until patch is applied
    deny all;
    # Or restrict to internal networks only
    # allow 10.0.0.0/8;
    # allow 192.168.0.0/16;
    # deny all;
}