/

CVE-2026-72688

Severity:

HIGH RISK

(7.5)

Missing Authentication (CWE-306) in OpenSign Server

CVE-2026-72688

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthorized access to stored documents

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 Server through version 2.37.0 contains a missing authentication check in the fileupload Parse cloud function. An unauthenticated remote attacker may request access tokens for caller-supplied URLs and read stored contract documents when the function is reachable.

Affected context

The issue occurs in OpenSign Server deployments that expose the fileupload Parse cloud function and use it to generate access tokens for stored files. Risk is higher when the function is reachable from an untrusted network and stored document URLs can be supplied without an authenticated session check.

Exploit preconditions

  • Attack surface: The remotely reachable fileupload Parse cloud function. - Required access: No authenticated account or valid session is required. - Trigger point: A request that causes the function to mint a file access

token for a caller-supplied URL.

  • Why exploitation is possible: The function uses a privileged MASTER_KEY

signing capability without first verifying the caller's identity or

authorization to access the requested document.

Why this happens

The underlying bug is an authorization boundary failure: a server-side function performs a privileged token-signing operation for an unauthenticated caller. This maps to CWE-306, Missing Authentication for Critical Function, because the function does not establish a user identity before granting access to protected resources. Treating caller-controlled file references as sufficient authorization allows the token-minting capability to bypass the normal document access controls.

Potential impact

  • An attacker may read confidential contract documents.
  • Unauthorized parties could access stored files across tenants or users,

depending on deployment and object-access boundaries.

  • Exposed documents could lead to privacy violations, business

confidentiality loss, or regulatory consequences.

  • Generated access tokens could enable continued access for their validity

period.

General mitigation guidance

Mitigation generally focuses on enforcing authentication and object-level authorization before any privileged file-token operation. Secure-by-default designs should require a validated session, verify that the requester owns or is permitted to access the specific document, and avoid deriving trust from caller-supplied URLs alone. Token issuance can be constrained by server-side document identifiers, tenant boundaries, short lifetimes, and least-privilege signing capabilities. Sensitive file endpoints should also minimize public exposure and apply consistent authorization middleware.

How teams detect issues like this

Detection can include static analysis and code review searches for cloud functions that use master or administrative keys before authentication and authorization checks. Reviewers can look for caller-controlled URLs, document identifiers, or token-generation paths that lack session and ownership validation. Runtime monitoring can flag anonymous requests to file-token endpoints, unusual document-access patterns, and access across tenant boundaries. API policy enforcement and automated security review tools can help identify unauthenticated sensitive operations.

Sources

SourceLink
github.comgithub.com/OpenSignLabs/OpenSign

Frequently asked

questions

Yes, when the affected cloud function is reachable by an untrusted remote

client. The described issue does not require a preexisting authenticated

session.

The attacker generally needs network access to the fileupload Parse cloud

function, but no valid user credentials are required.

Require authentication and document-level authorization before issuing any

file access token, and validate resource references against server-side

ownership or permission data.

Apply consistent authentication middleware to sensitive functions, enforce

tenant and object boundaries, restrict administrative key usage, and test

anonymous access paths in security and authorization reviews.

Find out what's already
exploitable in your codebase.