/

CVE-2026-92794

Severity:

HIGH RISK

(7.5)

Missing Authorization (CWE-862) in OpenSign Documents

CVE-2026-92794

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized 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

OpenSign fails to verify that a caller is authorized to access a document when one-time-password verification is disabled. An unauthenticated attacker who obtains a document identifier from a guest signing link may retrieve document metadata, signer and sender information, and valid download tokens.

Affected context

The vulnerability occurs in OpenSign's getDocument cloud function when OTP verification is disabled and document access relies on a document identifier supplied by the caller. Deployments that expose guest signing links or otherwise allow document identifiers to be obtained may be at greater risk if the function does not perform an independent authorization check.

Exploit preconditions

  • Attack surface: The OpenSign getDocument cloud function
  • Required access: No authenticated account is required; the attacker needs a valid document identifier, potentially obtained from a guest signing link
  • Trigger point: A request to retrieve document details while OTP verification is disabled
  • Why exploitation is possible: The function accepts the identifier without sufficiently validating that the caller is permitted to access the associated document

Why this happens

The underlying flaw is a missing authorization check in a document retrieval function. The application treats possession of a document identifier as sufficient authority instead of independently verifying the caller's identity and access rights. This behavior maps to CWE-862: Missing Authorization, where a protected operation lacks an effective permission check.

Potential impact

  • An unauthenticated attacker may obtain complete document details
  • Signer identities and sender information could be disclosed
  • Valid document download tokens could be exposed
  • Confidential documents may be downloaded or accessed by unauthorized parties
  • Privacy, regulatory, and business confidentiality risks could result

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the document retrieval boundary rather than relying on identifier secrecy or optional OTP checks.

Common defensive patterns include:

  • Require an authenticated identity or narrowly scoped signing capability before returning document data
  • Verify that the caller is authorized for the specific document and requested operation
  • Treat document identifiers and guest-link tokens as references, not proof of authorization
  • Return only the minimum fields needed for the current signing workflow
  • Use short-lived, scope-limited download credentials instead of reusable access tokens
  • Apply least-privilege permissions and invalidate exposed tokens when access conditions change

How teams detect issues like this

Organizations can identify similar authorization weaknesses through:

  • Static analysis and code review rules requiring permission checks before document retrieval
  • Review of cloud functions that accept object identifiers from unauthenticated or guest requests
  • Tests that compare access decisions for authorized, unauthorized, and unauthenticated callers
  • Monitoring for repeated document lookups, identifier enumeration, and token issuance without a verified identity
  • Policy enforcement requiring resource-level authorization and data minimization for sensitive APIs

Automated security testing and code review tools may help detect missing or inconsistently applied authorization checks.

Sources

SourceLink
github.comgithub.com/OpenSignLabs/OpenSign
github.comgithub.com/OpenSignLabs/OpenSign/blob/v2.41.0/apps/OpenSignServer/cloud/parsefunction/getDocument.js#L20-L32
github.comgithub.com/OpenSignLabs/OpenSign/issues/2218
vulncheck.comvulncheck.com/advisories/opensign-through-2.41.3-information-disclosure-via-getdocument

Frequently asked

questions

Yes. The affected cloud function can be reached remotely, and exploitation may be possible without authentication when an attacker has a document identifier from a guest signing link and OTP verification is disabled.

The attacker generally needs a valid document identifier or guest-link reference. The reported issue does not require a normal authenticated account.

Enforce an authorization decision for the specific document and requested operation before returning any metadata, signer information, or download capability.

Do not treat object identifiers or possession of links as authorization. Combine resource-level access checks, narrowly scoped tokens, minimal responses, and automated tests for unauthenticated and cross-user access.

Find out what's already
exploitable in your codebase.