CVE-2025-69907
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 · uneditedAn 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.
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 · high confidenceNewgen OmniDocs fails to enforce authentication on the /omnidocs/GetListofCabinet API endpoint, allowing any remote unauthenticated attacker to query this endpoint and receive sensitive internal configuration data including cabinet names and database-related metadata.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Newgen OmniDocs is installedLook for OmniDocs installation directories or check running web services on common ports (typically port 80/443 or 8080). Search for 'omnidocs' in process lists or installed applications.Affected if Newgen OmniDocs software is present in the environment
-
Identify the web application's base URLLocate the web server configuration or access logs that show the OmniDocs web application URL path, typically hosted under /omnidocs/ or similar context path.Affected if The web application is accessible via HTTP/HTTPS
-
Test unauthenticated access to the GetListofCabinet endpointSend a GET request to http://[host]/omnidocs/GetListofCabinet without providing any authentication headers, cookies, or session tokens.Affected if The endpoint returns an HTTP 200 response with cabinet names or database metadata without requiring login credentials
-
Verify sensitive data exposureExamine the response from the GetListofCabinet endpoint for cabinet names, database connection strings, or internal configuration metadata.Affected if The response contains cabinet names, database-related metadata, or internal configuration information accessible without authentication
-
Confirm no authentication is enforcedCompare responses with and without authentication tokens. If both return the same sensitive data, authentication is not enforced on this endpoint.Affected if Both authenticated and unauthenticated requests return identical sensitive configuration data
The environment is affected if the /omnidocs/GetListofCabinet endpoint responds with cabinet configuration or database metadata without requiring any authentication credentials.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement authentication and role-based access control on the /omnidocs/GetListofCabinet endpoint to ensure only authorized users can access cabinet configuration information.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69907 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-69907 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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