Skip to content

Broken Authorization: Any User Can Pause or Resume Any Poll via Poll ID Manipulation

High
lukevella published GHSA-4p93-v53r-vch3 Nov 19, 2025

Package

No package listed

Affected versions

< 4.5.4

Patched versions

>= 4.5.4

Description

Summary

An authorization flaw in the poll management feature allows any authenticated user to pause or resume any poll, regardless of ownership.
The system only uses the public pollId to identify polls, and it does not verify whether the user performing the action is the poll owner.
As a result, any user can disrupt polls created by others, leading to a loss of integrity and availability across the application.

Details

When a poll owner pauses or resumes their poll, the frontend sends a request containing only the pollId.
The backend endpoint responsible for handling these actions does not perform an authorization check to ensure the user owns the poll.
Affected Endpoints

  • /api/trpc/polls.pause

  • /api/trpc/polls.resume

Root Cause

  • Missing server-side validation of ownership or permissions before changing a poll’s state.

PoC

Test Environment Setup

Target: Local Rallly instance – http://192.168.11.109:3000/

User A (Victim): fairalien – Poll owner

User B (Attacker): hehe – Regular user

Steps to Reproduce

  1. User A (poll owner) creates a new poll.
    → Example URL: http://192.168.11.109:3000/polls/abc123

  2. User B (attacker) logs in with a regular account.

  3. User B intercepts a legitimate pause or resume request using a proxy tool.

1-intercept
  1. Modify pollId and forward request
2-modify
  1. Observe results
3-observe

Impact

This issue allows any logged-in user to pause or resume polls created by others, disrupting ongoing polls and manipulating availability.

Impact Type

  • Integrity: Unauthorized users can change the state of another user’s poll.

  • Availability: Attackers can repeatedly pause active polls, making them inaccessible to participants.

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

CVE ID

CVE-2025-65033

Weaknesses

Improper Authorization

The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Learn more on MITRE.

Authorization Bypass Through User-Controlled Key

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Learn more on MITRE.

Credits