Approved changes feed: RSS · Atom
cpe:2.3:a:rallly:rallly:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Rallly (5286db4a-aead-50c9-a265-0266dc250c18) |
|---|---|
| Product | Rallly (d0b30b43-73f9-5321-b555-2d284c1998ef) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-92565 |
vulnerable | 2026-10-13 12:28:53.463931 |
Rallly before 4.15.0 Information Disclosure via polls.get
MEDIUM (5.3)
Rallly before 4.15.0 contains an information disclosure vulnerability in the polls.get tRPC procedure that returns scheduled-event invitee names and email addresses to unauthenticated callers. Attackers can access a poll's urlId from public invite links to retrieve sensitive invitee information regardless of privacy settings.
Published: 2026-09-16T14:40:45.775Z
Updated: 2026-09-18T17:55:53.079Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-66027 |
vulnerable | 2026-06-08 07:39:21.136782 |
Rallly Information Disclosure Vulnerability in Participant API Leaks Names and Emails Despite Pro Privacy Settings
Rallly is an open-source scheduling and collaboration tool. Prior to version 4.5.6, an information disclosure vulnerability exposes participant details, including names and email addresses through the /api/trpc/polls.get,polls.participants.list endpoint, even when Pro privacy features are enabled. This bypasses intended privacy controls that should prevent participants from viewing other users’ personal information. This issue has been patched in version 4.5.6.
Published: 2025-11-29T00:43:02.452Z
Updated: 2025-12-01T14:11:22.446Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65034 |
vulnerable | 2026-06-08 07:39:20.650709 |
Rallly Improper Authorization Allows Reopening of Any Finalized Poll via Public pollId
HIGH (8.1)
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.
Published: 2025-11-19T17:26:59.038Z
Updated: 2025-11-19T20:20:04.793Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65033 |
vulnerable | 2026-06-08 07:39:20.650460 |
Rallly Broken Authorization: Any User Can Pause or Resume Any Poll via Poll ID Manipulation
HIGH (8.1)
Rallly is an open-source scheduling and collaboration tool. Prior to version 4.5.4, an authorization flaw in the poll management feature allows any authenticated user to pause or resume any poll, regardless of ownership. The system only uses the public pollId to identify polls, and it does not verify whether the user performing the action is the poll owner. As a result, any user can disrupt polls created by others, leading to a loss of integrity and availability across the application. This issue has been patched in version 4.5.4.
Published: 2025-11-19T17:26:44.807Z
Updated: 2025-11-19T20:03:45.344Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65032 |
vulnerable | 2026-06-08 07:39:20.650086 |
Rallly Has an IDOR Vulnerability in Participant Rename Function Allows Unauthorized Modification of Other Users’ Names
MEDIUM (6.5)
Rallly is an open-source scheduling and collaboration tool. Prior to version 4.5.4, an Insecure Direct Object Reference (IDOR) vulnerability allows any authenticated user to change the display names of other participants in polls without being an admin or the poll owner. By manipulating the participantId parameter in a rename request, an attacker can modify another user’s name, violating data integrity and potentially causing confusion or impersonation attacks. This issue has been patched in version 4.5.4.
Published: 2025-11-19T17:26:09.648Z
Updated: 2025-11-19T18:50:41.841Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65031 |
vulnerable | 2026-06-08 07:39:20.649626 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65030 |
vulnerable | 2026-06-08 07:39:20.649185 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65029 |
vulnerable | 2026-06-08 07:39:20.648805 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65028 |
vulnerable | 2026-06-08 07:39:20.648385 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65021 |
vulnerable | 2026-06-08 07:39:20.639704 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65020 |
vulnerable | 2026-06-08 07:39:20.639040 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-47781 |
vulnerable | 2026-06-08 07:27:14.849823 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.