CVE-2026-32823: CWE-352: Cross-Site Request Forgery (CSRF) in datacycle-engine dataCycle-CORE
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.
AI Analysis
Technical Summary
dataCycle-CORE, a data management system, has a CSRF vulnerability (CWE-352) in versions before 25.07.4. The vulnerability arises because state-changing operations are exposed through GET routes, which Rails does not protect with CSRF tokens. Browsers automatically send cookies on same-site top-level navigation, enabling attackers to force logged-in users to perform unintended actions by embedding malicious GET requests. Confirmed exploitation includes adding items to watch lists without CSRF tokens. Other GET mutation routes exist, including user impersonation and cache or translation state changes. The vulnerability is fixed in version 26.06.08.
Potential Impact
An attacker can cause a logged-in user to perform unauthorized state-changing actions via CSRF attacks exploiting unprotected GET routes. This can lead to unauthorized modifications such as inserting content into watch lists and potentially other state changes including user impersonation and cache or translation state changes. There is no direct confidentiality or availability impact reported. The CVSS score is 4.3 (medium severity), reflecting low complexity and user interaction required.
Mitigation Recommendations
A fix is available in dataCycle-CORE version 26.06.08. Users should upgrade to this version or later to remediate the vulnerability. Until then, consider restricting or monitoring access to affected GET endpoints and avoid embedding untrusted links that could trigger these requests. Since the vendor advisory does not specify other mitigations, patching is the primary recommended action.
CVE-2026-32823: CWE-352: Cross-Site Request Forgery (CSRF) in datacycle-engine dataCycle-CORE
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.
CVSS v3.1
Score 4.3medium
Affected software
pkg:github/datacycle-engine/dataCycle-CORERun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
dataCycle-CORE, a data management system, has a CSRF vulnerability (CWE-352) in versions before 25.07.4. The vulnerability arises because state-changing operations are exposed through GET routes, which Rails does not protect with CSRF tokens. Browsers automatically send cookies on same-site top-level navigation, enabling attackers to force logged-in users to perform unintended actions by embedding malicious GET requests. Confirmed exploitation includes adding items to watch lists without CSRF tokens. Other GET mutation routes exist, including user impersonation and cache or translation state changes. The vulnerability is fixed in version 26.06.08.
Potential Impact
An attacker can cause a logged-in user to perform unauthorized state-changing actions via CSRF attacks exploiting unprotected GET routes. This can lead to unauthorized modifications such as inserting content into watch lists and potentially other state changes including user impersonation and cache or translation state changes. There is no direct confidentiality or availability impact reported. The CVSS score is 4.3 (medium severity), reflecting low complexity and user interaction required.
Mitigation Recommendations
A fix is available in dataCycle-CORE version 26.06.08. Users should upgrade to this version or later to remediate the vulnerability. Until then, consider restricting or monitoring access to affected GET endpoints and avoid embedding untrusted links that could trigger these requests. Since the vendor advisory does not specify other mitigations, patching is the primary recommended action.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-16T17:35:36.697Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5e502f2a4a8d59895edd82
Added to database: 07/20/2026, 16:43:27 UTC
Last enriched: 07/20/2026, 16:58:22 UTC
Last updated: 07/21/2026, 04:28:51 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.