What is CVE-2026-113445?
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.
The record classifies CVE-2026-113445 under weakness class CWE-209. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 1 day ago.
Severity and exploitation probability
- CVSS v4.0 base score
- 6.9 — Medium (derived from score)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N - CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 3.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-11-16
Is CVE-2026-113445 being exploited?
It currently carries a trending score of 35 in the Threadlinqs vulnerability feed.
Affected products and versions
- VisualNet: visualTicket
How to fix CVE-2026-113445
No vendor patch reference has been recorded for CVE-2026-113445 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-113445
1 tracked threat in the Threadlinqs corpus references CVE-2026-113445, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, NVD, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.