/

CVE-2026-72545

Severity:

HIGH RISK

(7.5)

IDOR (CWE-639) in OpenSign Contact Record Update API

CVE-2026-72545

Deferred

Vulnerability type

Category:

Insecure Direct Object Reference

CWE:

CWE-639

Impact:

Unauthorized modification of contact records and loss of data integrity

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

An insecure direct object reference in OpenSign's updatecontacttour Parse cloud function allows unauthenticated remote attackers to update contact records without authorization checks. An attacker may corrupt or overwrite contact data belonging to other users by targeting their record identifiers.

Affected context

The issue occurs in OpenSign deployments using the updatecontacttour Parse cloud function to update contact records. Risk is present when the function accepts a client-supplied contact reference and processes the update without first authenticating the caller and verifying that the caller is authorized to modify the referenced record. The reported affected scope includes OpenSign through version 2.37.0.

Exploit preconditions

  • Attack surface: The remotely accessible updatecontacttour Parse cloud function
  • Required access: No authenticated account or valid credentials may be required
  • Trigger point: A request that invokes the contact-record update operation
  • Target selection: A caller-supplied identifier or reference for a contact record
  • Why exploitation is possible: The function performs insufficient authentication and object-level authorization checks before applying the update

Why this happens

The underlying bug is an object-level access control failure. The update function trusts a client-provided reference to select a contact record but does not establish the caller's identity or verify permission to modify that specific object. This behavior maps to CWE-639: Authorization Bypass Through User-Controlled Key, commonly associated with insecure direct object references.

Potential impact

  • An unauthenticated attacker may overwrite contact information
  • Contact records belonging to other users could be corrupted
  • Business workflows that depend on accurate contact data may be disrupted
  • The integrity and reliability of stored customer information could be reduced
  • Repeated abuse could cause broad data tampering across the application

General mitigation guidance

Mitigation generally focuses on enforcing authentication and object-level authorization at the server-side operation boundary.

Common defensive patterns include:

  • Require authentication before permitting contact-record changes
  • Derive the permitted user or tenant scope from the authenticated session rather than client input
  • Check authorization for the specific contact object before every update
  • Apply deny-by-default access policies to Parse cloud functions and data classes
  • Validate record identifiers and update fields against an explicit server-side schema
  • Limit service identities and database permissions according to least privilege
  • Avoid exposing predictable identifiers as the sole basis for authorization

How teams detect issues like this

Organizations can assess for this class of issue through:

  • Static analysis and code review searches for update operations using client-controlled object identifiers
  • Review of cloud functions for missing authentication and per-object authorization checks
  • API tests that compare access to owned, unrelated, and nonexistent records
  • Policy enforcement requiring authorization middleware on state-changing endpoints
  • Audit-log monitoring for anonymous updates, unusual record-target patterns, and high-volume contact modifications
  • Automated security testing or neutral code-review tools that flag missing object-level access controls

Sources

SourceLink
github.comgithub.com/OpenSignLabs/OpenSign

Frequently asked

questions

Yes. The affected cloud function is remotely reachable, and the reported issue indicates that an attacker may invoke it without authentication.

No account or credentials may be necessary. The key condition is the ability to reach the function and supply a target contact reference.

Enforce authentication and verify authorization for the specific contact record on the server before accepting any update.

Use deny-by-default access policies, derive ownership from trusted server-side identity data, test cross-user object access, and monitor state-changing API activity.

Find out what's already
exploitable in your codebase.