CVE-2026-113444 · Other
NO FIX YET · SEE WHAT TO DO
visualTicket's thumbnail generator uses the file parameter directly in an output path, so ../ sequences let a remote attacker write generated JPEG files outside the uploads folder, including the web root. The result is unauthorized file creation and possible overwriting of predictable files with matching names.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running visualTicket with the thumbnail generation feature exposed to users. The file parameter reaches the output path without restriction, so any caller who can reach that code path can write outside the uploads directory. Installations that do not expose thumbnail generation to untrusted users are less exposed; the sources do not say which configurations are affected beyond this.
Not affected if thumbnail-generation-disabled
Who cares php, self-hosted, visualtickets
20260817/uploads/user_temp_images/, especially in the web root20260817visualTicket 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.
This page as .md · .json · 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
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.