# CVE-2025-65021: Rallly Has Unauthorized Poll Finalization via Insecure Direct Object Reference (IDOR)

> Authenticated attackers can finalize other users' polls via IDOR, disrupting workflows and altering data integrity in Rallly.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 19 Nov 2025
- **Updated:** 19 Nov 2025
- **Also known as:** GHSA-x7w2-g548-4qg8

## What is CVE-2025-65021?

CVE-2025-65021 is a critical missing authorization vulnerability in lukevella rallly, published on 19 Nov 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. Prior to version 4.5.4, an Insecure Direct Object Reference (IDOR) vulnerability exists in the poll finalization feature of the application. Any authenticated user can finalize a poll they do not own by manipulating the pollId parameter in the request. This allows unauthorized users to finalize other users’ polls and convert them into events without proper authorization checks, potentially disrupting user workflows and causing data integrity and availability issues. This issue has been patched in version 4.5.4.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2025-65021?

It affects 1 product.


Products: Rallly Rallly.

## How do I fix CVE-2025-65021?

No fix has been published for CVE-2025-65021 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-65021 being exploited?

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

## Other vulnerabilities in lukevella rallly

- [CVE-2025-47781](https://insights.sbomify.com/CVE-2025-47781/): Rallly Insufficient Password Login Token Entropy Leads to Account Takeover (critical 9.8)
- [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-65021 and fix it if it is affected.

What it is: CVE-2025-65021 is a critical missing authorization vulnerability in lukevella rallly, published on 19 Nov 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-65021 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-65021/ (Markdown: https://insights.sbomify.com/CVE-2025-65021/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-65021
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-65021
- OSV: https://osv.dev/vulnerability/CVE-2025-65021

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-65021/
Summaries are generated and may contain mistakes; the official description above is the record.