CVE-2026-113455: visualTicket: KSeF API token shown unmasked in admin panel

AWAITING NVD
Published November 16, 2026
CISO Take

visualTicket, a Polish ticketing platform, displays the KSeF API integration secret in plain text in a pre-filled field on the admin settings edit form (CWE-497, exposure of sensitive system information). We found no evidence that this product is an AI/ML system. The 'ml_ui' category looks like a misclassification, so it is unlikely to affect AI pipelines unless one is integrated with KSeF through it. No CVSS score or EPSS data is available, it is not in CISA KEV, and no public exploit or scanner template exists, so exploitation urgency is low. The risk is credential disclosure to anyone who can open the admin panel or view a shoulder-surfed screen, session recording or screenshot. Upgrade to version 20260817 or later, and rotate the KSeF API token if admin access was ever shared or exposed.

Sources:NVDcert.plATLAS

What is the risk?

Low to medium. Exploitation requires access to the admin settings panel, so an attacker needs privileged or compromised admin credentials, or access to screens, recordings or browser caches. There is no CVSS or EPSS score and no known exploitation. The impact is exposure of a third-party integration secret that could give access to Poland's National e-Invoicing System (KSeF) on behalf of the organization. The AI/ML relevance is minimal.

How does the attack unfold?

Initial Access
The attacker obtains access to the visualTicket admin panel through a valid or compromised admin session, or captures an admin screen.
AML.T0012
Credential Discovery
The attacker opens the 'KSeF - Token API' edit form and reads the unmasked secret.
AML.T0055
Impact
The attacker uses the stolen token to access the KSeF e-invoicing API, enabling data exposure or fraudulent invoicing.
AML.T0048.000

How severe is it?

CVSS 3.1
N/A
EPSS
0.3%
chance of exploitation in 30 days
Higher than 25% of all CVEs
Exploitation Status
No known exploitation
Sophistication
Trivial

What should I do?

6 steps
  1. Upgrade visualTicket to version 20260817 or later, which fixes the issue.

  2. Rotate the KSeF API token, since it may already have been displayed to admins or captured in screen recordings, browser autofill, session replay tools or support screenshots.

  3. Restrict admin panel access with least privilege, MFA and IP allowlisting.

  4. Review KSeF API audit logs for unexpected calls or sessions.

  5. Make sure session replay, analytics or monitoring tools do not capture admin pages.

  6. See the CERT.PL advisory for details.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

NIST AI RMF
MANAGE 2.3-Risk treatment and response to identified risks

Frequently Asked Questions

What is CVE-2026-113455?

visualTicket, a Polish ticketing platform, displays the KSeF API integration secret in plain text in a pre-filled field on the admin settings edit form (CWE-497, exposure of sensitive system information). We found no evidence that this product is an AI/ML system. The 'ml_ui' category looks like a misclassification, so it is unlikely to affect AI pipelines unless one is integrated with KSeF through it. No CVSS score or EPSS data is available, it is not in CISA KEV, and no public exploit or scanner template exists, so exploitation urgency is low. The risk is credential disclosure to anyone who can open the admin panel or view a shoulder-surfed screen, session recording or screenshot. Upgrade to version 20260817 or later, and rotate the KSeF API token if admin access was ever shared or exposed.

Is CVE-2026-113455 actively exploited?

No confirmed active exploitation of CVE-2026-113455 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-113455?

1. Upgrade visualTicket to version 20260817 or later, which fixes the issue. 2. Rotate the KSeF API token, since it may already have been displayed to admins or captured in screen recordings, browser autofill, session replay tools or support screenshots. 3. Restrict admin panel access with least privilege, MFA and IP allowlisting. 4. Review KSeF API audit logs for unexpected calls or sessions. 5. Make sure session replay, analytics or monitoring tools do not capture admin pages. 6. See the CERT.PL advisory for details.

What systems are affected by CVE-2026-113455?

This vulnerability affects the following AI/ML architecture patterns: Admin web interfaces, Third-party API integrations.

What is the CVSS score for CVE-2026-113455?

No CVSS score has been assigned yet.

What is the AI security impact?

Affected AI Architectures

Admin web interfacesThird-party API integrations

MITRE ATLAS Techniques

AML.T0055Unsecured Credentials

Compliance Controls Affected

NIST AI RMF: MANAGE 2.3

What are the technical details?

Original Advisory

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.

Exploitation Scenario

An attacker or malicious insider gains access to a low-trust admin account, or captures a screen share or recording of the settings page. They open the 'KSeF - Token API' edit form, where the secret is pre-filled and unmasked, and copy it. They then use the token to call the KSeF API and read or issue invoice data. An AI-driven workflow such as invoice-processing automation could be affected only if it consumed this same token.

Weaknesses (CWE)

CWE-497 — Exposure of Sensitive System Information to an Unauthorized Control Sphere: The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.

  • [Architecture and Design, Implementation] Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user. All error message text should be HTML entity encoded before being written to the log file to protect against potential cross-site scripting attacks against the viewer of the logs

Source: MITRE CWE corpus.

Timeline

Published
November 16, 2026
Last Modified
November 17, 2026
First Seen
November 16, 2026

Related Vulnerabilities