Skip to main content
VulnerabilityPublished

CVE-2026-113451: visualTicket is vulnerable to Cross-Site Request Forgery (CSRF) across multiple endpoints

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-113451· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 20260817 when convenient.

Data as of 16 Nov 2026, 17:21 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (CERT-PL)CVSS 4.06.9
Patch
Available – fixed in 20260817
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade visualTicket to 20260817.

Affected software

ProductAffectedFixed in
VisualNetvisualTicketAffected
  • =0
Fixed in
  • 20260817

AI-suggested

Upgrade to visualTicket version 20260817 or later, which partially addresses the issue by requiring POST requests with CSRF tokens for settings changes and bulk refunds, and by setting session cookies with SameSite=Lax. Users should verify that these mitigations are in place and avoid using vulnerable versions.

Description

visualTicket is affected by a Cross-Site Request Forgery (CSRF) vulnerability across multiple endpoints. The vulnerability allows state-changing operations to be executed via GET requests without CSRF protection, enabling a remote attacker to trick an authenticated user into performing unintended actions. Partial mitigation was introduced in version 20260817, requiring POST requests with CSRF tokens for settings changes and bulk refunds, and setting the session cookie with SameSite=Lax to limit cross-site requests.

References

Community reviews

Loading reviews…