Skip to main content
Vulnerability Database/CVE-2026-111350

CVE-2026-111350: Papermark Auth Bypass Vulnerability

CVE-2026-111350 is an authorization bypass flaw in Papermark through version 0.22.0 that lets authenticated attackers delete viewer groups and share links across teams. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111350 Overview

CVE-2026-111350 is a missing authorization vulnerability [CWE-862] in Papermark through version 0.22.0. The flaw affects the data room viewer group API. Authenticated users can delete other teams' viewer groups and share links without belonging to those teams. Attackers who know a victim team's data room and group identifiers can issue DELETE requests, read group links, or rewrite group document permissions across tenant boundaries. The issue stems from team membership checks that validate only the existence of a team, not the acting user's membership in it.

Critical Impact

Authenticated tenants can tamper with viewer groups, share links, and document permissions belonging to other teams, breaking multi-tenant isolation in Papermark data rooms.

Affected Products

  • Papermark through version 0.22.0
  • Data room viewer group API endpoints under pages/api/teams/[teamId]/datarooms/[id]/groups/[groupId]/
  • Multi-tenant Papermark deployments sharing viewer groups and links

Discovery Timeline

  • 2026-10-15 - CVE-2026-111350 published to the National Vulnerability Database (NVD)
  • 2026-10-16 - Last updated in the NVD database

Technical Details for CVE-2026-111350

Vulnerability Analysis

The vulnerability is a Missing Authorization issue in the Papermark data room viewer group API. The affected handlers accept a teamId, data room id, and groupId from the URL path. They then perform the requested action (delete, read links, or update group document permissions) without verifying that the authenticated session user belongs to the supplied team. Any authenticated Papermark user who learns another team's identifiers can mutate that team's groups and links. The practical impact is cross-tenant tampering: deleted share links, lost viewer group configurations, and unauthorized rewrites of document access policy inside shared data rooms.

Root Cause

The handlers in pages/api/teams/[teamId]/datarooms/[id]/groups/[groupId]/index.ts and .../links.ts query the team record by teamId only, treating a successful lookup as authorization. The membership check against the acting userId is absent, so the API trusts the path parameter instead of the session. The fix recorded in commit b81cf62f390cda112f35538eb09e54b5f728b74a replaces the team lookup with a direct userTeam lookup keyed by the composite userId_teamId, enforcing membership before any mutation.

Attack Vector

Exploitation is network-based and requires an authenticated Papermark account. The attacker enumerates or obtains a target teamId, data room id, and groupId, then calls the vulnerable endpoints to delete the viewer group, read group link data, or rewrite group document permissions in the victim tenant.

typescript
// Patch excerpt: enforce user-team membership before mutating a dataroom group
// File: pages/api/teams/[teamId]/datarooms/[id]/groups/[groupId]/index.ts
const userId = (session.user as CustomUser).id;

try {
  const teamAccess = await prisma.userTeam.findUnique({
    where: {
      userId_teamId: {
        userId: userId,
        teamId: teamId,
      },
    },
  });

  if (!teamAccess) {
    return res.status(403).end("Unauthorized to access this team");
  }
}

Source: GitHub Commit: Bug Fix

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-111350

Indicators of Compromise

  • DELETE requests to /api/teams/{teamId}/datarooms/{id}/groups/{groupId} where the authenticated session user is not a member of {teamId}.
  • Unexpected disappearance of viewer groups or share links in a tenant that did not initiate the change.
  • GET or PUT requests to .../groups/{groupId}/links originating from accounts outside the owning team.

Detection Strategies

  • Correlate the teamId path parameter against the authenticated user's team memberships in access logs and alert on mismatches.
  • Review audit logs for group deletions and document-permission changes that lack a corresponding administrative action from a team member.
  • Monitor for sequential enumeration of groupId or teamId values from a single authenticated session.

Monitoring Recommendations

  • Enable verbose API access logging for all /api/teams/*/datarooms/*/groups/* routes, including user identity and team membership context.
  • Alert on HTTP 403 spikes following deployment of the patch, which may indicate prior probing attempts.
  • Track viewer group and link lifecycle events in the application database and reconcile them against expected tenant activity.

How to Mitigate CVE-2026-111350

Immediate Actions Required

  • Upgrade Papermark beyond version 0.22.0 to a release that includes commit b81cf62f390cda112f35538eb09e54b5f728b74a.
  • Audit data room viewer groups, group links, and document permissions for unauthorized changes made before patching.
  • Rotate any share links exposed through the vulnerable endpoints and notify affected teams.

Patch Information

The fix is tracked in the Papermark repository. See the GitHub Commit: Bug Fix which replaces the permissive team lookup with a userTeam membership check in pages/api/teams/[teamId]/datarooms/[id]/groups/[groupId]/index.ts. Additional context is available in the VulnCheck Advisory: Authorization Flaw and the HackMD Article on Authz Issues.

Workarounds

  • Restrict access to the Papermark instance to trusted authenticated users while the patch is rolled out.
  • Add a reverse-proxy or middleware check that compares the session user's team membership against the teamId path parameter before forwarding requests to the affected endpoints.
  • Temporarily disable or remove sensitive viewer groups and share links in production data rooms until the upgrade is complete.
bash
# Upgrade Papermark to a patched release containing commit b81cf62
git fetch --all --tags
git checkout main
git pull origin main
npm install
npx prisma migrate deploy
npm run build
npm run start

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.