---
id: "CVE-2026-113451"
page: "https://infrastack.ai/live/CVE-2026-113451"
kind: "vulnerability"
aliases: ["CVE-2026-113451"]
title: "visualTicket: state-changing endpoints accept GET requests, enabling cross-site request forgery"
severity: "medium"
cvss: 6.9
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["other", "self-hosted", "visualticket"]
not_affected_if: ["not-visualticket"]
published_at: "2026-11-16T13:17:20+00:00"
first_seen_at: "2026-11-16T13:37:56+00:00"
updated_at: "2026-11-16T13:38:45+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-113451", "first_seen_at": "2026-11-16T13:37:56+00:00"}]
exploit_sources: []
---

# visualTicket: state-changing endpoints accept GET requests, enabling cross-site request forgery

Link for people: https://infrastack.ai/live/CVE-2026-113451 (this .md is for agents)

visualTicket exposes state-changing operations through GET requests with no CSRF protection. A remote attacker can trick a logged-in user, including an administrator, into opening a prepared URL that performs actions with the victim's session cookie.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Confirm whether the installed visualTicket version is earlier than `20260817`.
- Check whether settings changes or bulk refunds can still be triggered by a GET request to the application.
- Check the session cookie attributes for `SameSite=Lax` or stricter.

## Fix

- Move to `20260817` or later, which requires POST with a CSRF token for settings changes and bulk refunds.
- The sources say the session cookie is set with `SameSite=Lax`, which only partly limits the risk. Other state-changing endpoints may remain GET-based: unknown.

## Timeline

- 2026-11-16T13:37:56+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-113451

## From the sources

visualTicket is vulnerable to Cross-Site Request Forgery (CSRF) across multiple endpoints. State-changing operations are exposed via GET requests without any CSRF protection. A remote attacker can persuade an authenticated user (including administrator) into navigating to a prepared URL, causing the victim's browser to issue requests that carry the active session cookie and perform unintended actions.




This issue was partially addressed in version 20260817: settings changes and bulk refunds require POST with a CSRF token, and the session cookie is set with SameSite=Lax, which limits cross-site requests.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
