Skip to main content
VulnerabilityPublished

CVE-2026-113451: VisualNet visualTicket · Cross-Site Request Forgery

Affects VisualNet visualTicketSource CVE Database V5

0
Compare

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

Data as of 16 Nov 2026, 12:35 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 VisualNet visualTicket to 20260817.

Affected software

ProductAffectedFixed in
VisualNetvisualTicketAffected
  • =0
Fixed in
  • 20260817

AI-suggested

Upgrade to version 20260817 or later, where partial fixes have been implemented. This includes requiring POST requests with CSRF tokens for sensitive operations and setting the session cookie with SameSite=Lax. These mitigations reduce the risk of CSRF attacks by limiting cross-site request forgery vectors. No additional vendor advisories indicate further actions are required.

Description

VisualNet visualTicket versions prior to 20260817 are vulnerable to Cross-Site Request Forgery (CSRF) attacks on multiple endpoints. State-changing operations are exposed via GET requests without CSRF protection, allowing remote attackers to trick authenticated users into performing unintended actions. Partial mitigation was introduced in version 20260817 by requiring POST requests with CSRF tokens for certain operations and setting the session cookie with SameSite=Lax.

References

Community reviews

Loading reviews…