Skip to main content
VulnerabilityPublished

CVE-2026-113453: VisualNet visualTicket · Missing Authorization

Affects VisualNet visualTicketSource CVE Database V5

0
Compare

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

Data as of 16 Nov 2026, 12:35 UTC

CVSS 4.0 base score
6.3Medium
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.3
Patch
Available – fixed in 20260817
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

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

Upgrade to VisualNet visualTicket version 20260817 or later, where this missing authorization issue has been fixed. Until then, restrict access to the static path serving invoice PDFs or implement additional access controls to prevent unauthorized downloads.

Description

CVE-2026-113453 is a missing authorization vulnerability in VisualNet's visualTicket product. The issue allows unauthenticated remote attackers to download invoice PDF files directly via their URLs because these files are served from a web-accessible static path without session or authorization checks. Authorization is only enforced on the invoice registry page, not on the PDF file serving endpoint. This vulnerability was fixed in version 20260817.

References

Community reviews

Loading reviews…