Skip to content

IDOR in Participant Deletion Endpoint Allows Unauthorized Removal of Poll Participants

Moderate
lukevella published GHSA-f8jc-6746-ww95 Nov 19, 2025

Package

No package listed

Affected versions

< 4.5.4

Patched versions

>= 4.5.4

Description

Summary

An insecure direct object reference (IDOR) vulnerability allows any authenticated user to delete arbitrary participants from polls without ownership verification. The endpoint relies solely on a participant ID to authorize deletions, enabling attackers to remove other users (including poll owners) from polls. This impacts the integrity and availability of poll participation data.

Details

The vulnerability exists in the Rallly application’s participant deletion endpoint. The backend fails to validate ownership or authorization before processing a deletion request. It assumes that anyone with a valid participant ID has the right to perform the delete action.

Using a previously disclosed information disclosure issue (GHSA-xw47-6mpg-5hww

PoC

Test Environment Setup:

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

Victim (User A): fairalien (Poll owner)

Attacker (User B): hehe (Normal participant)

Steps to Reproduce:

1- Obtain participant IDs:
Use the previous vulnerability (GHSA-xw47-6mpg-5hww
2-get-participant-id

2- Intercept a legitimate delete request:
Capture the request made when the attacker deletes their own participation.
3-intercept-request

3- Modify the request and forward it:

4-change-id-and-forward

Replace the attacker's participant ID with another user’s ID (e.g., fairalien) and send the tampered request to the server. The server accepts it and deletes the targeted participant.

4- Observe result:

5-deleted succesffuly

The victim participant is removed from the poll even though the attacker does not own it.

Impact

This vulnerability allows unauthorized users to delete arbitrary participants from polls, including poll owners. It affects data integrity (by modifying participant data without permission) and availability (by removing participants and potentially disrupting poll functionality).

Severity

Moderate

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
Low
Availability
Low

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:L/A:L

CVE ID

CVE-2025-65029

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.

Missing Authorization

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

Credits