visualTicket is vulnerable to information exposure through an error message in the order creation functionality. Because detailed data-layer exceptions are returned to the client instead of being logged server-side only, a remote unauthenticated attacker can submit a valid checkout request with an invalid payment_type value, causing the application to return a detailed SQL/ORM error that discloses the database name, table and column names, query structure, and foreign key constraint name.
This issue was fixed in version 20260817.
0.5% estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-209Generation of Error Message Containing Sensitive Information
Show the promptExplain CVE-2026-113445 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-113445?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-113445?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-113445 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.