Skip to main content
VulnerabilityPublished

CVE-2026-113449: visualTicket is vulnerable to information exposure through JSONP on session-bound cart service

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-113449· Medium 6.3

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

Data as of 16 Nov 2026, 17:22 UTC

CVSS 4.0 base score
6.3Medium
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.3
Patch
Available – fixed in 20260817
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/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

The vulnerability has been mitigated in visualTicket version 20260817 by setting the session cookie with the SameSite=Lax attribute. This prevents other websites from reading the victim's cart session data via cross-site requests. Users and administrators should upgrade to version 20260817 or later to ensure this protection is in place.

Description

visualTicket has a vulnerability involving information exposure through JSONP on session-bound cart service endpoints. Sensitive session data including session id, cart id, item ids, ticket/event metadata, quantities, and prices are exposed inside a script wrapper. Because the symfony session token can be passed in the URL, an attacker who obtains this token can read the victim's cart session data. This issue was mitigated in version 20260817 by setting the session cookie with SameSite=Lax, preventing other websites from accessing the cart data.

References

Community reviews

Loading reviews…