CVE-2026-113451 · Other
NO FIX YET · SEE WHAT TO DO
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.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Any visualTicket deployment where logged-in staff, especially administrators, can be tricked into opening a link from outside the application. The sources say the 20260817 release only fixes settings changes and bulk refunds, so other endpoints may still be exposed. Installations that do not run visualTicket can skip it.
Not affected if not-visualticket
Who cares self-hosted, visualticket
20260817.SameSite=Lax or stricter.20260817 or later, which requires POST with a CSRF token for settings changes and bulk refunds.SameSite=Lax, which only partly limits the risk. Other state-changing endpoints may remain GET-based: unknown.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.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.