CVE-2026-32807

In dataCycle-CORE before version 25.07.3, there are no limits on login attempts via browser or API. Account locking is disabled and requests are not rate-limited, allowing continuous password guessing.

In dataCycle-CORE before version 25.07.3, an authenticated low-privileged API user can supply custom URLs in password reset or confirmation flows. These URLs are embedded in emails without host allowlisting.

In dataCycle-CORE before version 26.06.08, the application exposes server-side state changes through `GET` routes. Because browsers automatically send cookies on same-site top-level navigation and Rails does not apply CSRF protections to `GET`, an attacker can force a logged-in victim to modify application state by embedding a link, image, iframe, or redirect to one of these endpoints.

In dataCycle-CORE before version 25.07.3, an authenticated API user can use their access token to query the collection API for permissions of another user by supplying their email. If the target user has collections, they may be exposed. In V4, a known collection can be modified via add/remove items without proper authorization.

In dataCycle-CORE before version 25.07.3, the documentation and static Markdown renderer improperly handles attacker-controlled path segments. An unauthenticated attacker can use directory traversal sequences to read arbitrary .md files outside the intended docs or static directories.

In dataCycle-CORE before version 25.07.3, a Standard user can enumerate other users' names and email addresses through the /users/search endpoint, even though direct access to user profiles is denied.

Vulnerability in dataCycle-CORE before version 26.06.08 (including 25.07.3). The /remote_render endpoint does not restrict which partials can be rendered, allowing a low-privileged authenticated user to access server-side rendered admin content.

Reflected DOM XSS vulnerability in dataCycle-CORE before version 25.07.3. An unauthenticated attacker can inject arbitrary HTML into flash notifications on public routes, and the toast component injects that content into the DOM via innerHTML, allowing script execution via a crafted link.