/

CVE-2025-69907

Severity:

HIGH RISK

(7.5)

Missing Authorization / Access Control in Newgen OmniDocs

CVE-2025-69907

Awaiting Analysis

Vulnerability type

Category:

Missing Authorization / Access Control

CWE:

CWE-284

Impact:

Unauthenticated Information Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Newgen OmniDocs exposes the /omnidocs/GetListofCabinet API endpoint without enforcing authentication or access control, allowing unauthenticated users to query it directly.

A remote attacker can leverage this to retrieve cabinet names and database-related metadata, unintentionally disclosing internal configuration details that can support further targeted attacks.

Affected context

The vulnerability occurs in deployments of Newgen OmniDocs where the /omnidocs/GetListofCabinet endpoint is reachable over the network and is not protected by authentication or authorization middleware.

It primarily affects environments that expose OmniDocs to untrusted networks (such as the public internet or flat internal networks) and rely on the application to enforce access control, rather than placing the API behind additional gateways or network segmentation.

Exploit preconditions

  • Attack surface: Network-accessible OmniDocs API endpoint at /omnidocs/GetListofCabinet
  • Required access: None; the issue is exploitable without authentication or valid user credentials
  • Trigger point: Sending an HTTP request to the vulnerable endpoint
  • Why exploitation is possible: The endpoint lacks proper authentication and authorization checks, so the server returns internal configuration data to any requester regardless of identity or permissions

Why this happens

This issue stems from missing or incomplete enforcement of authorization controls on a sensitive API endpoint, aligning with CWE-284: Improper Access Control.

The /omnidocs/GetListofCabinet endpoint is treated as if it were public, and no authentication or role-based checks are applied before returning cabinet and database-related metadata.

At a design level, the application does not consistently centralize access control policy, causing this endpoint to bypass expected protections and expose internal configuration data.

Potential impact

  • An attacker may enumerate cabinet names and related organizational structures within the document management system.
  • An attacker could gather database-related metadata useful for profiling the backend environment.
  • An attacker can map internal deployment details, aiding in targeted exploitation of other weaknesses.
  • An attacker may combine the leaked information with additional vulnerabilities to escalate impact (e.g., privilege escalation or data exfiltration).

General mitigation guidance

Effective mitigation generally focuses on enforcing strict access control around all configuration- and metadata-related endpoints:

  • Ensure that access to functional and configuration APIs (such as cabinet listing endpoints) is gated behind robust authentication and session validation by default.
  • Apply centralized authorization checks that verify user roles and permissions before returning internal or administrative information.
  • Follow a "deny by default" API design, requiring explicit opt-in for public endpoints and treating configuration and enumeration endpoints as sensitive.
  • Limit the amount and granularity of metadata returned by APIs, exposing only what is necessary for legitimate use cases.
  • Complement application-level controls with network-level protections such as API gateways, reverse proxies, and segmentation to reduce direct exposure of administrative APIs.

How teams detect issues like this

Organizations can detect and monitor for similar access control weaknesses by:

  • Using static analysis or API linting tools to flag controller methods or routes that handle sensitive data but lack authentication/authorization decorators or middleware.
  • Reviewing routing and security configuration to ensure no "catch-all allow" rules inadvertently mark administrative or metadata endpoints as public.
  • Conducting targeted security testing and API fuzzing to probe unauthenticated access to endpoints that return configuration, enumeration data, or internal metadata.
  • Implementing logging and monitoring that highlight unauthenticated access to endpoints returning unusually detailed system or database information.

Sources

SourceLink
github.comgithub.com/CBx216/CVE-Newgen-Software-Advisories/blob/main/CVE-2025-69907.md
newgensoft.comnewgensoft.com/

Frequently asked

questions

Yes. If the OmniDocs instance is network-accessible (for example, over the internet or a shared internal network), a remote attacker can access the endpoint without prior authentication.

No. The core issue is the absence of authentication and authorization on the /omnidocs/GetListofCabinet endpoint, so no valid user account or session token is required.

Apply consistent, centralized authentication and authorization checks to all endpoints that expose configuration, metadata, or administrative information, and treat such endpoints as sensitive by default.

Adopt a secure-by-default API design that denies access unless explicitly permitted, use standardized security middleware for all routes, regularly test for unauthenticated access to sensitive endpoints, and enforce these practices through code review and automated security testing in CI/CD pipelines.

Find out what's already
exploitable in your codebase.