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.
Published: 2026-07-20
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The flaw allows a malicious web site to force an authenticated user to issue GET requests that alter application state, such as adding items to a watch list or performing privileged actions. By embedding a URL in an image tag, link, or frame, the attacker can trigger server‑side changes without the user’s consent that compromises data integrity and could facilitate more advanced attacks if additional mutation routes are exposed.

Affected Systems

The vulnerability exists in the datacycle‑engine dataCycle‑CORE module in all releases up to and including version 25.07.3. Upgrades to 26.06.08 and later contain a fix that removes state‑changing GET endpoints.

Risk and Exploitability

The CVSS score of 4.3 indicates moderate severity, while the EPSS score is <1% and the issue is not listed in CISA KEV. The likely attack vector is a classic CSRF scenario: the victim’s browser automatically sends session cookies when the attacker’s malicious page loads a link or image pointing to the vulnerable GET endpoint. Successful exploitation requires the victim to be logged into dataCycle, but no additional credentials are needed beyond the user’s session.

Generated by OpenCVE AI on July 30, 2026 at 19:10 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade dataCycle‑CORE to version 26.06.08 or later to remove unprotected GET mutation routes.
  • Reconfigure any remaining GET endpoints that modify state to require a CSRF token, or convert them; if upgrade is not possible, deploy a web‑application firewall or paths and enforce same‑site cookie policies to mitigate accidental state changes.
  • Ensure the application’s cookie settings enforce SameSite=Lax or Strict to prevent automatic cross‑site cookie transmission.

Generated by OpenCVE AI on July 30, 2026 at 19:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 23 Jul 2026 21:45:00 +0000

Type Values Removed Values Added
First Time appeared Datacycle-engine
Datacycle-engine datacycle-core
Vendors & Products Datacycle-engine
Datacycle-engine datacycle-core

Mon, 20 Jul 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 20 Jul 2026 16:45:00 +0000

Type Values Removed Values Added
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.
Title dataCycle State-Changing GET Endpoints Enable CSRF
Weaknesses CWE-352
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N'}


Subscriptions

Datacycle-engine Datacycle-core
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-20T19:05:22.754Z

Reserved: 2026-03-16T17:35:36.697Z

Link: CVE-2026-32823

cve-icon Vulnrichment

Updated: 2026-07-20T19:04:58.011Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-30T19:15:04Z

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)