CVE-2026-113449 · Package
NO FIX YET · SEE WHAT TO DO
The visualTicket cart service returns session-bound data, including the session id, cart id, item ids, prices and quantities, wrapped in a JSONP script response. An attacker who obtains the Symfony session token can read the cart session token and cart contents.
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.
Sites that run visualTicket's session-bound cart service endpoints can expose cart data through JSONP. The source says the mitigation is the session cookie set with SameSite=Lax, and the sources name no other affected configuration. Sites that do not use these endpoints or already set SameSite=Lax are not described as exposed.
Not affected if samesite-lax-cookie
Who cares symfony, ticketing, visualtickets
SameSite=Lax in the Symfony session configuration.20260817: the session cookie is set with SameSite=Lax, which the source says prevents other websites from reading cart data of the victim's session.visualTicket is vulnerable to information exposure through JSONP on session-bound cart service endpoints. Session-bound data (including the session id, cart id, item ids, ticket/event metadata, quantities and prices) is returned inside a script wrapper, and since the symfony session token can also be passed in the URL, a remote attacker who obtains the token can read the cart session token and cart data.
This issue was mitigated in version 20260817: the session cookie is set with SameSite=Lax, which prevents other websites from reading cart data of the victim’s session.
This page as .md · .json · 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/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.