Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-65032: CWE-639: Authorization Bypass Through User-Controlled Key in lukevella rallly

0
Medium
VulnerabilityCVE-2025-65032cvecve-2025-65032cwe-639
Published: Wed Nov 19 2025 (11/19/2025, 17:26:09 UTC)
Source: CVE Database V5
Vendor/Project: lukevella
Product: rallly

Description

Rallly is an open-source scheduling and collaboration tool. Prior to version 4.5.4, an Insecure Direct Object Reference (IDOR) vulnerability allows any authenticated user to change the display names of other participants in polls without being an admin or the poll owner. By manipulating the participantId parameter in a rename request, an attacker can modify another user’s name, violating data integrity and potentially causing confusion or impersonation attacks. This issue has been patched in version 4.5.4.

AI-Powered Analysis

AILast updated: 11/26/2025, 18:06:25 UTC

Technical Analysis

CVE-2025-65032 is an Insecure Direct Object Reference (IDOR) vulnerability classified under CWE-639, affecting Rallly, an open-source scheduling and collaboration platform. Prior to version 4.5.4, the application fails to properly authorize requests to rename poll participants. Specifically, any authenticated user can manipulate the participantId parameter in a rename request to change the display names of other users in a poll, even if they are not the poll owner or an administrator. This bypasses intended access controls, violating data integrity by allowing unauthorized modification of user-visible information. The flaw does not expose confidential data or disrupt availability but can cause confusion, misattribution, or impersonation within collaborative environments. The vulnerability has a CVSS 3.1 base score of 6.5, reflecting medium severity, with an attack vector of network, low attack complexity, requiring privileges (authenticated user), no user interaction, and unchanged scope. No known exploits are currently reported in the wild. The issue was addressed and patched in Rallly version 4.5.4 by enforcing proper authorization checks on participant rename operations.

Potential Impact

For European organizations, this vulnerability primarily threatens data integrity within collaborative scheduling environments. Unauthorized renaming of participants can lead to confusion, miscommunication, and potential impersonation, undermining trust in the tool and complicating coordination efforts. In sectors where accurate participant identification is critical—such as healthcare, finance, or government—this could have operational repercussions or facilitate social engineering attacks. While confidentiality and availability are not directly impacted, the integrity breach can indirectly affect decision-making and workflow efficiency. Organizations relying on Rallly for internal or external collaboration risk reputational damage and reduced user confidence if this vulnerability is exploited. The requirement for authentication limits exposure to internal or trusted users, but insider threats or compromised accounts could leverage this flaw.

Mitigation Recommendations

The primary mitigation is to upgrade Rallly to version 4.5.4 or later, where the vulnerability is patched. Organizations should audit their deployments to identify affected versions and prioritize timely updates. Additionally, implement strict access controls and monitoring on user accounts to reduce the risk of compromised credentials being used to exploit this flaw. Employ logging and alerting on participant rename actions to detect anomalous behavior indicative of exploitation attempts. Educate users about the risks of impersonation and encourage verification of participant identities through secondary channels when critical decisions depend on poll outcomes. For environments where immediate patching is not feasible, consider restricting poll participant rename permissions to trusted roles or disabling rename functionality temporarily. Regularly review and test authorization mechanisms in collaboration tools to prevent similar IDOR vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-13T15:36:51.683Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 691e026793c808727dc91d68

Added to database: 11/19/2025, 5:46:15 PM

Last enriched: 11/26/2025, 6:06:25 PM

Last updated: 1/7/2026, 8:49:30 AM

Views: 49

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats