Authenticated poll-data tampering via unchecked participant identifier
Published Nov 19, 2025 · Updated Nov 19, 2025
Authorization bypass in Luke Vella Rallly before 4.5.4 allows remote authenticated users to rename other poll participants. The /api/trpc/polls.participants.rename backend trusts the client-supplied participantId without checking ownership or modification permission. Any signed-in participant who can capture a legitimate rename request can substitute another participant's identifier, enabling poll-data tampering and impersonation.
Summary
What happened
Authorization bypass in Luke Vella Rallly before 4.5.4 allows remote authenticated users to rename other poll participants. The /api/trpc/polls.participants.rename backend trusts the client-supplied participantId without checking ownership or modification permission. Any signed-in participant who can capture a legitimate rename request can substitute another participant's identifier, enabling poll-data tampering and impersonation.
The record
- CVE
- CVE-2025-65032
- Published
- Nov 19, 2025
- Updated
- Nov 19, 2025
- Vendor
- Luke Vella
- Product
- Rallly
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 19, 2025CVE publishedPublication date reported by the CVE source.
- Nov 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.5.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Participant rename request-manipulation proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo