CVE-2026-32823
MediumCVSS 4.3Exploitation Probability (EPSS)
Low risk1th percentile - higher than 1% of all known CVEs
Summary
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.
Risk Assessment
An attacker can perform unauthorized operations such as adding items to watch lists, impersonating administrators, or changing cache/translation state without the victim's consent.
Recommendation
Update dataCycle-CORE to version 26.06.08 or later. Consider adding CSRF protection for sensitive `GET` endpoints.
Other vulnerabilities in dataCycle-CORE
See all- CVE-2026-32825High
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.
- CVE-2026-32824High
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.
- CVE-2026-32821High
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.
- CVE-2026-32820High
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.
- CVE-2026-32819Medium
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.
- CVE-2026-32806High
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.
- CVE-2026-32822Medium
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.
- CVE-2026-32807High
Vulnerability in dataCycle-CORE before version 26.06.08 (including 25.07.3). Anyone with a DataLink UUID can fetch the attached text file directly, even if the link is expired, the caller is unauthenticated, or the normal show flow would have denied access.
Original NVD description (English source)
dataCycle is a data management system for centrally storing, managing, searching, finding, and distributing data. In dataCycle-CORE, the module handling core processing and framework rules, before and including version 25.07.3, 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. This was confirmed on the target with a normal `Standard` account: a cross-site-style `GET` to `watch_lists/:id/add_item?thing_id=...` inserted content into a watch list with no CSRF token. Additional `GET` mutation routes exist in the codebase, including user impersonation for authorized admins and cache or translation state changes. This is patched in version 26.06.08.