VISUALTICKET · CVE-2026-113455 · Other
NO FIX YET · SEE WHAT TO DO
The visualTicket admin settings form for the KSeF Token API prefills the field with the real integration secret instead of a masked value. Anyone who can open that admin page can read the token in plain text.
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.
Sites running visualTicket with the KSeF integration configured, where admin users can open the KSeF Token API settings form. The secret is exposed to anyone with admin panel access, so exposure is limited to admin-level accounts. Installations without the KSeF integration, or where the token is not set, are not affected.
Not affected if auth-required, no-ksef-integration
Who cares ksef, visualticket, wordpress
20260817 (per the advisory's note that this issue was fixed in version 20260817)visualTicket displays secret token value in admin settings panel. The "KSeF - Token API" edit form renders a pre-filled field containing the actual KSeF API integration secret without any masking.
This issue was fixed in version 20260817.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/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.