CVE-2026-32823 dataCycle State-Changing GET Endpoints Enable CSRF
Attackers can force logged-in users to modify application state or impersonate users via malicious GET requests due to missing CSRF protections.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-32823?
CVE-2026-32823 is a medium-severity vulnerability in datacycle-engine dataCycle-CORE, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-352
Which versions are affected by CVE-2026-32823?
How do I fix CVE-2026-32823?
No fix has been published for CVE-2026-32823 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-32823 being exploited?
There is no known exploitation of CVE-2026-32823 in the wild and no public exploit code.