CVE-2026-113451: Cross-Site Request Forgery in VisualNet visualTicket
VisualNet visualTicket exposes state-changing operations across multiple endpoints through GET requests without CSRF protection. A remote attacker can induce an authenticated user, including an administrator, to navigate to a crafted URL, causing the browser to submit requests with the active session cookie and perform unintended actions. Versions before 20260817 are affected; version 20260817 only partially addresses the vulnerability by requiring POST requests with CSRF tokens for settings changes and bulk refunds and setting the session cookie to SameSite=Lax.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits unauthorized state changes under the victim's authenticated session. The scope of available actions depends on the vulnerable endpoint and the victim's privileges, potentially including administrative operations. Version 20260817 protects settings changes and bulk refunds but does not fully resolve the vulnerability across all affected endpoints.
Mitigation
If you can’t patch tonight, do this now.
Version 20260817 requires POST requests with CSRF tokens for settings changes and bulk refunds and sets the session cookie to SameSite=Lax. These protections reduce exposure but do not eliminate CSRF on remaining state-changing GET endpoints: SameSite=Lax can still allow session cookies on cross-site top-level GET navigation. No comprehensive workaround is identified.
Remediation
Patch, then assume compromise.
Deploy version 20260817 to obtain the documented partial protections, but do not consider this a complete fix. No version that fully resolves all affected endpoints is identified in the available information.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-113451 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-113451 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-113451?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-113451.
- Is there a patch for CVE-2026-113451?
- Deploy version 20260817 to obtain the documented partial protections, but do not consider this a complete fix. No version that fully resolves all affected endpoints is identified in the available information.
- How severe is CVE-2026-113451?
- CVE-2026-113451 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 0.23% (14th percentile) as of Nov 17, 2026.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.