Skip to main content
Menu
CVEs

CVE

VisualNet visualTicket cross-site request forgery in GET endpoints

CVE-2026-113451EUVD-2026-126304GHSA-XH5C-3FV3-9267

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/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
14/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

VisualNet's visualTicket is vulnerable to cross-site request forgery across multiple endpoints, where state-changing actions are exposed via GET requests without CSRF protection. A remote attacker who does not need to log in can trick an authenticated user, including an administrator, into opening a prepared URL, which makes the victim's browser perform unintended actions using their active session.

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

Original description

visualTicket is vulnerable to Cross-Site Request Forgery (CSRF) across multiple endpoints. State-changing operations are exposed via GET requests without any CSRF protection. A remote attacker can persuade an authenticated user (including administrator) into navigating to a prepared URL, causing the victim's browser to issue requests that carry the active session cookie and perform unintended actions.

This issue was partially addressed in version 20260817: settings changes and bulk refunds require POST with a CSRF token, and the session cookie is set with SameSite=Lax, which limits cross-site requests.

cve.now Index

14Pcve.now Index 14 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure7/25Reachable over the network without a login · 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 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 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-113451 (Cross-Site Request Forgery 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-113451 (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-113451 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-113451 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-113451
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-113451"}.

Timeline

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

    Exploitation: none · Automatable: no · 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-113451

Is CVE-2026-113451 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-113451?

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

How do I fix CVE-2026-113451?

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