Skip to content

Improper Authorization Allows Reopening of Any Finalized Poll via Public pollId

High
lukevella published GHSA-5fp2-pv2j-rqpc Nov 19, 2025

Package

No package listed

Affected versions

< 4.5.4

Patched versions

>= 4.5.4

Description

Summary

An improper authorization vulnerability allows any authenticated user to reopen finalized polls belonging to other users by manipulating the pollId parameter. This can disrupt events managed by other users and compromise both availability and integrity of poll data.

Details

In the affected endpoint responsible for reopening finalized polls, the application does not verify that the user performing the action is the poll owner. As a result, any authenticated user can intercept a legitimate request to reopen their own poll, modify the pollId parameter to reference another user’s poll, and successfully reopen it.

The vulnerability exists due to a missing ownership check on the backend for the pollId parameter.

Vulnerable endpoint :

  • /api/trpc/polls.reopen

PoC

Test Environment Setup

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

Victim (User A): fairalien — Poll owner

Attacker (User B): hehe — Normal user

Steps to Reproduce

  1. As User A, create and finalize a poll.

  2. As User B, intercept your own legitimate “reopen poll” request .

1-intercept
  1. Modify the pollId parameter in the request body to use the victim’s poll ID and Forward the modified request.
2-modify
  1. Observe that the victim’s finalized poll has been successfully reopened and no events appear.
3-observe

Impact

This is an Insecure Direct Object Reference (IDOR) vulnerability that allows unauthorized reopening of finalized polls.
Attackers can:

  • Reopen other users’ finalized events without permission.

  • Potentially disrupt ongoing scheduling or availability processes.

  • Undermine trust and integrity of event data in the system.

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-65034

Weaknesses

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