Exposure of KSeF API Integration Secret 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.
Exploit prediction score: < 1% (0.315% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Exposure of KSeF API Integration Secret in visualTicket | |
| First Time appeared |
Visualnet
Visualnet visualticket |
|
| Weaknesses | CWE-497 | |
| CPEs | cpe:2.3:a:visualnet:visualticket:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Visualnet
Visualnet visualticket |
|
| References |
| |
| Metrics |
cvssV4_0
|