Skip to main content
Menu
CVEs

CVE

VisualNet visualTicket information disclosure in checkout error handling

CVE-2026-113445EUVD-2026-126298GHSA-CJ36-W337-J9JG

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

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 20260817
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 20260817.

Published
Last modified
Reference
Last checked
27/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

Remotely, without logging in, an attacker can send a checkout request with an invalid payment_type value to visualTicket, which makes the application return a detailed database error. That error reveals database, table, and column names, query structure, and a foreign key constraint name, which an attacker could use to plan further attacks.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

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.

cve.now Index

27Pcve.now Index 27 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 20260817.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-113445 (Information Exposure Through Error Message in visualTicket), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-113445 (entry last updated 2026-11-16):
Affected:
- VisualNet visualTicket: fixed in 20260817
Fixed versions: 20260817.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-113445 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-113445 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://cert.pl/posts/2026/11/CVE-2026-113443
- https://systembiletowy.pl/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-113445
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-113445"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • VisualNet visualTicket

    fixed in 20260817

Evidence 4

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Link
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-113445

Is CVE-2026-113445 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-113445?

visualTicket: before 20260817.Source: cve.now feed data

How do I fix CVE-2026-113445?

Upgrade to a fixed version: 20260817.Source: cve.now feed data