CVE-2025-47781
CVE-2025-47781 is a critical-severity vulnerability in Rallly with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-331.
Key facts
- Severity: Critical (CVSS 3.x base score 9.8)
- EPSS exploit prediction: 1% (41st percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-14949
- Weakness: CWE-331
- Affected product: Rallly
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2025-47781?
- 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.
- How severe is CVE-2025-47781?
- CVE-2025-47781 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2025-47781 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2025-47781?
- CVE-2025-47781 affects Rallly. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2025-47781?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- Does CVE-2025-47781 have an EU (EUVD) identifier?
- Yes. CVE-2025-47781 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-14949.
- When was CVE-2025-47781 published?
- CVE-2025-47781 was published on 2025-05-14 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:rallly:rallly:*:*:*:*:*:*:*:*
More vulnerabilities in Rallly
- CVE-2025-65021 — Critical (CVSS 9.1): Rallly is an open-source scheduling and collaboration tool. Prior to version 4.5.4, an Insecure Direct Object Reference…
- CVE-2025-65034 — High (CVSS 8.1): Rallly is an open-source scheduling and collaboration tool. Prior to version 4.5.4, an improper authorization…
- CVE-2025-65033 — High (CVSS 8.1): Rallly is an open-source scheduling and collaboration tool. Prior to version 4.5.4, an authorization flaw in the poll…
- CVE-2025-65029 — High (CVSS 8.1): Rallly is an open-source scheduling and collaboration tool. Prior to version 4.5.4, an insecure direct object reference…
- CVE-2025-65030 — High (CVSS 7.1): Rallly is an open-source scheduling and collaboration tool. Prior to version 4.5.4, an authorization flaw in the…
- CVE-2025-66027 — Medium (CVSS 6.5): Rallly is an open-source scheduling and collaboration tool. Prior to version 4.5.6, an information disclosure…
Other CWE-331 vulnerabilities
- CVE-2020-36925 — Critical (CVSS 9.8): Arteco Web Client DVR/NVR contains a session hijacking vulnerability with insufficient session ID complexity that…
- CVE-2024-47945 — Critical (CVSS 9.8): The devices are vulnerable to session hijacking due to insufficient entropy in its session ID generation algorithm.…
- CVE-2024-25730 — Critical (CVSS 9.8): Hitron CODA-4582 and CODA-4589 devices have default PSKs that are generated from 5-digit hex values concatenated with a…
- CVE-2023-49599 — Critical (CVSS 9.8): An insufficient entropy vulnerability exists in the salt generation functionality of WWBN AVideo dev master commit…
- CVE-2022-34294 — Critical (CVSS 9.8): totd 1.5.3 uses a fixed UDP source port in upstream queries sent to DNS resolvers. This allows DNS cache poisoning…
- CVE-2021-41615 — Critical (CVSS 9.8): websda.c in GoAhead WebServer 2.1.8 has insufficient nonce entropy because the nonce calculation relies on the…