/

CVE-2026-72692

Severity:

HIGH RISK

(7.5)

Broken Access Control (CWE-862) in OpenSign Server

CVE-2026-72692

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized document workflow termination and evidentiary record falsification

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

A missing authorization check in OpenSign Server allows an unauthenticated remote attacker to decline any accessible in-flight document through the declinedoc Parse cloud function.

The attacker may also supply an arbitrary user attribution, terminating document workflows and falsifying the associated decline record when the function is reachable and accepts the request.

Affected context

The vulnerability occurs in OpenSign Server deployments through version 2.37.0 where the declinedoc Parse cloud function is exposed and processes document-decline requests without adequately verifying the caller's identity or authority over the target document. Risk is highest when unauthenticated clients can reach the function and documents are in a state that permits decline operations.

Exploit preconditions

  • Attack surface: The remotely accessible declinedoc Parse cloud function
  • Required access: No authentication is required when the vulnerable function is exposed as described
  • Target condition: The target document must be accessible to the function and remain in an in-flight state
  • Trigger point: Processing a document-decline request
  • Why exploitation is possible: The function updates IsDeclined, DeclineReason, and DeclineBy without binding the operation to an authenticated, authorized caller

Why this happens

The underlying bug is a missing authorization decision at a state-changing server-side operation. The function accepts document and attribution data, changes workflow state, and stores a caller-supplied user pointer without verifying that the requester is authenticated and permitted to act on the document.

This behavior maps to CWE-862: Missing Authorization, because access control is not enforced before a protected action and related record updates are performed.

Potential impact

  • An unauthenticated attacker may irreversibly decline in-flight documents
  • Business workflows could be terminated without the document owner's approval
  • Decline reasons and attribution records could be falsified
  • Audit, compliance, or evidentiary records could be undermined
  • Affected users or organizations could experience denial of service for document processing

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every state-changing server-side function.

Common defensive patterns include:

  • Require authentication before processing document-decline operations
  • Verify that the authenticated principal is authorized for the specific document and workflow state
  • Derive attribution fields from trusted session or identity claims rather than caller-supplied values
  • Apply server-side validation and immutable audit controls to decline reasons and actor identity
  • Use deny-by-default policies for cloud functions and explicitly expose only required operations
  • Limit service-account and backend privileges so a compromised endpoint cannot alter unrelated documents
  • Add authorization tests for object ownership, role boundaries, and state-transition rules

How teams detect issues like this

Organizations can assess for this class of issue through:

  • Static analysis and code review rules that flag state-changing functions lacking authentication or authorization checks
  • Review of cloud-function handlers for caller-controlled object identifiers and attribution fields
  • Tests that attempt document actions across users, roles, and workflow states
  • API policy checks requiring authentication and object-level authorization for protected operations
  • Audit-log monitoring for declines that lack a matching authenticated actor or show unusual cross-user activity
  • Automated security review tools that identify missing authorization enforcement and client-controlled identity fields

Sources

SourceLink
github.comgithub.com/OpenSignLabs/OpenSign

Frequently asked

questions

Yes. When the vulnerable cloud function is reachable without authentication, an attacker can remotely submit a decline operation for an accessible in-flight document.

The described issue does not require a valid account. The attacker needs network access to the exposed function and a target document that the function can process.

Enforce authentication and object-level authorization before changing document state. The server should also derive the decline actor from the authenticated identity instead of trusting a request-supplied user reference.

Use deny-by-default endpoint policies, centralized authorization checks, explicit workflow-state validation, and automated tests that verify cross-user and unauthenticated access is rejected.

Find out what's already
exploitable in your codebase.