Skip to main content
VulnerabilityPublished

CVE-2026-113456: VisualNet visualTicket · Generation of Error Message Containing Sensitive Information

Affects VisualNet visualTicketSource CVE Database V5

0
Compare

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

Data as of 16 Nov 2026, 12:35 UTC

CVSS 4.0 base score
5.1Medium
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.05.1
Patch
Available – fixed in 20260817
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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 VisualNet visualTicket to 20260817.

Affected software

ProductAffectedFixed in
VisualNetvisualTicketAffected
  • =0
Fixed in
  • 20260817

AI-suggested

This vulnerability has been fixed in VisualNet visualTicket version 20260817. Users should upgrade to this version or later to remediate the issue. No additional mitigation steps are required once the patch is applied.

Description

CVE-2026-113456 is a vulnerability in VisualNet's visualTicket cinema report generator where error messages disclose sensitive information. An authenticated admin user can trigger detailed error pages by supplying an invalid date_from value, revealing full SQL SELECT statements and PHP DateTime parsing exceptions. This information disclosure could aid attackers in understanding the database structure. The issue was fixed in version 20260817.

References

Community reviews

Loading reviews…