CVE-2026-113444 json
Path Traversal in visualTicket
published yesterday modified yesterday also EUVD-2026-126297
- cvss
- 5.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
visualTicket is vulnerable to Path Traversal in the thumbnail generation mechanism. The file parameter is used directly when constructing the output filesystem path without restriction to the uploads directory, allowing a remote attacker to use ../ sequences to escape /uploads/user_temp_images/ and write the generated JPEG file to other writable locations, including the web root. This allows unauthorized creation of JPEG files outside the intended uploads directory, leading to file-space pollution and potential overwriting of predictable resources with matching names.
This issue was fixed in version 20260817.
Patch / fix
- VisualNet visualTicket 20260817
Is CVE-2026-113444 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-17).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N |
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- VisualNet visualTicket
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
cert.pl
/posts/2026/11/CVE-2026-113443
third-party-advisory
-
systembiletowy.pl
/
product
Sources
- CVE List CVE-2026-113444
- NVD CVE-2026-113444
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.