CVE
ScreenTinker stored XSS in kiosk button hijacks admin sessions
- Exploited
- No known exploitation
- Fix
- Fixed in 3.2.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.2.4.
Summary
ScreenTinker, before version 3.2.4, has a stored cross-site scripting flaw in its kiosk page button handling. An attacker with low-privilege login and kiosk page edit rights can reach it remotely by saving a javascript: URL as a page button, and when an administrator clicks that button, the script runs in the dashboard and can hijack the administrator's session and take control of the instance.
Original description
ScreenTinker before 3.2.4 contains a stored cross-site scripting vulnerability in the GET /api/kiosk/:id/render endpoint that allows users with kiosk page edit rights to store javascript: URLs in page buttons. Attackers can trigger script execution in the dashboard origin when an administrator activates the button, hijacking the victim's session and taking full control of the instance.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.1/10CVSS 5.1
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.2.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132752 (ScreenTinker before 3.2.4 Stored XSS via Kiosk Page Button javascript: URL), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132752 (entry last updated 2026-11-18):
Affected:
- screentinker screentinker: fixed in 3.2.4
Fixed versions: 3.2.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132752 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132752 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/screentinker/screentinker/security/advisories/GHSA-g46x-g9mc-g2hp
- https://github.com/screentinker/screentinker/commit/c498e67bcc551764de9fb132a8b9ff5d2224134f
- https://github.com/screentinker/screentinker/releases/tag/v3.2.4
- https://www.vulncheck.com/advisories/screentinker-before-3.2.4-stored-xss-via-kiosk-page-button-javascript-url
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132752
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132752"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- screentinker screentinker
fixed in 3.2.4
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · screentinker/screentinker · Advisory GHSA-g46x-g9mc-g2hp |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132752 |
| Record | NVD · CVE-2026-132752 |
| Other links 3 | |
| Patch | GitHub · screentinker/screentinker · Commit c498e67b |
| Repository | GitHub · screentinker/screentinker · Release v3.2.4 |
| Link | vulncheck.com · advisories/screentinker-before-3.2.4-stored-xss-via-kiosk-page-button-javascript-url |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132752
Is CVE-2026-132752 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-132752?
screentinker: before 3.2.4.Source: cve.now feed data
How do I fix CVE-2026-132752?
Upgrade to a fixed version: 3.2.4.Source: cve.now feed data