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-65034: CWE-639: Authorization Bypass Through User-Controlled Key in lukevella rallly

0
High
VulnerabilityCVE-2025-65034cvecve-2025-65034cwe-639
Published: Wed Nov 19 2025 (11/19/2025, 17:26:59 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 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. This issue has been patched in version 4.5.4.

AI-Powered Analysis

AILast updated: 11/26/2025, 18:05:31 UTC

Technical Analysis

CVE-2025-65034 is an authorization bypass vulnerability classified under CWE-639 (Authorization Bypass Through User-Controlled Key) affecting Rallly, an open-source scheduling and collaboration platform. The flaw exists in versions prior to 4.5.4, where the application fails to properly verify user permissions when reopening finalized polls. Specifically, any authenticated user can manipulate the pollId parameter in requests to reopen polls that belong to other users without proper authorization checks. This bypass allows unauthorized reopening of finalized polls, which can disrupt scheduled events, cause confusion among participants, and compromise the integrity and availability of poll data. The vulnerability does not affect confidentiality directly but impacts integrity and availability significantly. Exploitation requires the attacker to be authenticated but does not require additional user interaction, making it relatively easy to exploit within an organization. The issue was identified and patched in version 4.5.4, which enforces proper authorization checks on poll reopening operations. No known exploits have been reported in the wild as of the publication date. The CVSS v3.1 score is 8.1, reflecting high severity due to network attack vector, low attack complexity, required privileges, and no user interaction. The vulnerability's root cause is insufficient authorization validation when processing user-controlled keys (pollId), a common security weakness in web applications managing multi-user resources.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the integrity and availability of collaborative scheduling data. Organizations relying on Rallly for event coordination may experience unauthorized reopening of finalized polls, leading to event disruptions, scheduling conflicts, and potential loss of trust among users. This can affect internal operations, customer-facing scheduling, and cross-organizational collaboration. The disruption could cascade into operational inefficiencies and reputational damage, especially for sectors dependent on precise scheduling such as healthcare, education, and public services. Since the vulnerability requires authentication, insider threats or compromised user accounts could be leveraged to exploit this flaw. The lack of confidentiality impact reduces risk of data leakage but does not diminish the operational impact. Given the open-source nature of Rallly, organizations using customized or self-hosted deployments may face challenges in timely patching, increasing exposure duration.

Mitigation Recommendations

European organizations should immediately upgrade all Rallly instances to version 4.5.4 or later where the vulnerability is patched. In addition, organizations should audit user permissions and access controls related to poll management to ensure least privilege principles are enforced. Implement monitoring and alerting for unusual poll reopening activities, especially those initiated by users who do not own the polls. Consider network segmentation and access restrictions to limit authenticated user capabilities where possible. For self-hosted deployments, verify that all dependencies and integrations are compatible with the patched version to avoid operational disruptions. Conduct security awareness training to reduce risks from compromised credentials. Finally, maintain an incident response plan to quickly address any exploitation attempts or operational impacts stemming from this vulnerability.

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.684Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 691e026793c808727dc91d70

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

Last enriched: 11/26/2025, 6:05:31 PM

Last updated: 1/7/2026, 8:15:45 AM

Views: 56

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