Skip to content

IDOR in Vote Update Endpoint Allows Unauthorized Manipulation of Participant Votes

Moderate
lukevella published GHSA-pchc-v5hg-f5gp 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 modify other participants’ votes in polls without authorization. The backend relies solely on the participantId parameter to identify which votes to update, without verifying ownership or poll permissions. This allows an attacker to alter poll results in their favor, directly compromising data integrity.

Details

The Rallly application fails to validate ownership before accepting vote change requests. By leveraging the previously disclosed information disclosure issue (GHSA-xw47-6mpg-5hww
Once these IDs are known, the attacker can intercept their own legitimate “change vote” request and modify the participantId field to reference another participant. The server does not check whether the authenticated user actually owns the targeted participant record, thus accepting and applying the malicious update.

Vulnerable Flow:

Attacker enumerates participant IDs via the prior information disclosure vulnerability.

Attacker intercepts a legitimate vote-change request.

Attacker replaces their own participant ID with another user’s ID (e.g., poll owner’s).

The modified request is sent to the server, which processes the update successfully.

Victim’s votes are altered without their knowledge or consent.

This results in an attacker being able to manipulate poll outcomes arbitrarily.

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 (Regular participant)

Steps to Reproduce:

  1. Obtain participant IDs:

Use the information disclosure vulnerability (GHSA-xw47-6mpg-5hww
1-get-participant id

  1. Intercept a legitimate vote update request:
    Capture the request while the attacker updates their own vote selection.
2-intercept-request
  1. Modify the request and Forward the modified request:
    Replace the attacker’s participantId with another user’s (e.g., the poll owner’s participantId) and send it to the server.
3-modify and forward

The request is processed successfully, updating the victim’s votes.

  1. Verify results:
4-results

The poll now reflects modified votes for the victim’s account.

Impact

This vulnerability allows unauthorized users to manipulate other participants’ votes, directly altering poll results. It compromises data integrity, as attackers can falsify voting outcomes, and may also impact trust and fairness in collaborative decision-making processes.

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
High
Availability
None

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:N

CVE ID

CVE-2025-65028

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