Cross-Site Request Forgery in visualTicket
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| VisualNet | visualTicket | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Cross-Site Request Forgery in visualTicket | |
| First Time appeared |
Visualnet
Visualnet visualticket |
|
| Weaknesses | CWE-352 | |
| CPEs | cpe:2.3:a:visualnet:visualticket:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Visualnet
Visualnet visualticket |
|
| References |
| |
| Metrics |
cvssV4_0
|
Cross-Site Request Forgery (CSRF)
No data.
No data.
No data.
No data.