# CVE-2025-47781: Rallly Insufficient Password Login Token Entropy Leads to Account Takeover > Attackers can brute force low-entropy login tokens to take over user accounts in the Rallly scheduling application. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 14 May 2025 - **Updated:** 14 May 2025 - **Also known as:** GHSA-gm8g-3r3j-48hv ## What is CVE-2025-47781? CVE-2025-47781 is a critical authentication bypass vulnerability in lukevella rallly, published on 14 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Rallly is an open-source scheduling and collaboration tool. Versions up to and including 3.22.1 of the application features token based authentication. When a user attempts to login to the application, they insert their email and a 6 digit code is sent to their email address to complete the authentication. A token that consists of 6 digits only presents weak entropy however and when coupled with no token brute force protection, makes it possible for an unauthenticated attacker with knowledge of a valid email address to successfully brute force the token within 15 minutes (token expiration time) and take over the account associated with the targeted email address. All users on the Rallly applications are impacted. As long as an attacker knows the user's email address they used to register on the app, they can systematically take over any user account. For the authentication mechanism to be safe, the token would need to be assigned a complex high entropy value that cannot be bruteforced within reasonable time, and ideally rate limiting the /api/auth/callback/email endpoint to further make brute force attempts unreasonable within the 15 minutes time. As of time of publication, no patched versions are available. Weakness: CWE-331 (Insufficient Entropy) ## Which versions are affected by CVE-2025-47781? It affects 1 product. Products: Rallly Rallly. ## How do I fix CVE-2025-47781? No fix has been published for CVE-2025-47781 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-47781 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47781 exists. ## Other vulnerabilities in lukevella rallly - [CVE-2025-65021](https://insights.sbomify.com/CVE-2025-65021/): Rallly Has Unauthorized Poll Finalization via Insecure Direct Object Reference (IDOR) (critical 9.1) - [CVE-2025-65029](https://insights.sbomify.com/CVE-2025-65029/): Rallly Has an IDOR Vulnerability in Participant Deletion Endpoint Allows Unauthorized Removal of Poll Participants (high 8.1) - [CVE-2025-65033](https://insights.sbomify.com/CVE-2025-65033/): Rallly Broken Authorization: Any User Can Pause or Resume Any Poll via Poll ID Manipulation (high 8.1) - [CVE-2025-65034](https://insights.sbomify.com/CVE-2025-65034/): Rallly Improper Authorization Allows Reopening of Any Finalized Poll via Public pollId (high 8.1) - [CVE-2025-66027](https://insights.sbomify.com/CVE-2025-66027/): Rallly Information Disclosure Vulnerability in Participant API Leaks Names and Emails Despite Pro Privacy Settings (high 7.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-47781 and fix it if it is affected. What it is: CVE-2025-47781 is a critical authentication bypass vulnerability in lukevella rallly, published on 14 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47781 exists. Affected product: lukevella rallly. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-47781/ (Markdown: https://insights.sbomify.com/CVE-2025-47781/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-47781 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-47781 - OSV: https://osv.dev/vulnerability/CVE-2025-47781 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-47781/ Summaries are generated and may contain mistakes; the official description above is the record.