Skip to main content
VulnerabilityPublished

CVE-2026-113445: visualTicket is vulnerable to information exposure through an error message in the order creation

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-113445· Medium 6.9

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

Data as of 16 Nov 2026, 17:34 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: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

This vulnerability has been fixed in visualTicket version 20260817. Users should upgrade to this version or later to remediate the issue. No additional mitigation steps are indicated in the available data.

Description

visualTicket has an information exposure vulnerability in its order creation functionality. When a remote unauthenticated attacker submits a checkout request with an invalid payment_type value, the application returns detailed SQL/ORM error messages. These error messages disclose sensitive database information such as database name, table and column names, query structure, and foreign key constraint names. The issue was fixed in version 20260817.

References

Community reviews

Loading reviews…