CVE-2025-47781 Rallly Insufficient Password Login Token Entropy Leads to Account Takeover

Critical 9.8 Published Updated

Attackers can brute force low-entropy login tokens to take over user accounts in the Rallly scheduling application.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

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

Which versions are affected by CVE-2025-47781?

It affects 1 product.

Products include 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.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2025-47781 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47781 exists.

Sources

Also known as GHSA-gm8g-3r3j-48hv.

Is CVE-2025-47781 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free