Jexactyl has Stored DOM Cross-Site Scripting (XSS) via unescaped JSON in Blade template
Key facts
- Attack vector
- Local
- Privileges required
- High
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-79.
Summary
Jexactyl is a customisable game management panel and billing system. Commits after 025e8dbb0daaa04054276bda814d922cf4af58da and before e28edb204e80efab628d1241198ea4f079779cfd inject server-side objects into client-side JavaScript through resources/views/templates/wrapper.blade.php. Using unescaped {!! json_encode(...) !!} without safe encoding flags allows string values to break out of the JavaScript context and be interpreted as HTML/JS by the browser. If any serialized fields contain attacker-controlled content, such as a username, display name, or site config value, a malicious payload will execute arbitrary script for any user viewing the page (stored DOM XSS). This issue has been patched by commit e28edb204e80efab628d1241198ea4f079779cfd.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Jexactyl | Jexactyl | >= 025e8dbb0daaa04054276bda814d922cf4af58da, < e28edb204e80efab628d1241198ea4f079779cfd | — | No fix listed | CNA |
- Jexactyl VendorJexactyl Affected >= 025e8dbb0daaa04054276bda814d922cf4af58da, < e28edb204e80efab628d1241198ea4f079779cfd Fixed in — No fix listed CNA
CPE configurations NVD · 10
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:jexactyl:jexactyl:*:*:*:*:*:*:*:* | up to 3.8.0 | Vulnerable | Jexactyl |
| cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta1:*:*:*:*:*:* | 4.0.0 beta1 | Vulnerable | Jexactyl |
| cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta2:*:*:*:*:*:* | 4.0.0 beta2 | Vulnerable | Jexactyl |
| cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta3:*:*:*:*:*:* | 4.0.0 beta3 | Vulnerable | Jexactyl |
| cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta4:*:*:*:*:*:* | 4.0.0 beta4 | Vulnerable | Jexactyl |
| cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta5:*:*:*:*:*:* | 4.0.0 beta5 | Vulnerable | Jexactyl |
| cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta6:*:*:*:*:*:* | 4.0.0 beta6 | Vulnerable | Jexactyl |
| cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta7:*:*:*:*:*:* | 4.0.0 beta7 | Vulnerable | Jexactyl |
| cpe:2.3:a:jexactyl:jexactyl:4.0.0:rc1:*:*:*:*:*:* | 4.0.0 rc1 | Vulnerable | Jexactyl |
| cpe:2.3:a:jexactyl:jexactyl:4.0.0:rc2:*:*:*:*:*:* | 4.0.0 rc2 | Vulnerable | Jexactyl |
- cpe:2.3:a:jexactyl:jexactyl:*:*:*:*:*:*:*:* Versions up to 3.8.0 Vulnerable ·Jexactyl
- cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta1:*:*:*:*:*:* Versions 4.0.0 beta1 Vulnerable ·Jexactyl
- cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta2:*:*:*:*:*:* Versions 4.0.0 beta2 Vulnerable ·Jexactyl
- cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta3:*:*:*:*:*:* Versions 4.0.0 beta3 Vulnerable ·Jexactyl
- cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta4:*:*:*:*:*:* Versions 4.0.0 beta4 Vulnerable ·Jexactyl
- cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta5:*:*:*:*:*:* Versions 4.0.0 beta5 Vulnerable ·Jexactyl
- cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta6:*:*:*:*:*:* Versions 4.0.0 beta6 Vulnerable ·Jexactyl
- cpe:2.3:a:jexactyl:jexactyl:4.0.0:beta7:*:*:*:*:*:* Versions 4.0.0 beta7 Vulnerable ·Jexactyl
- cpe:2.3:a:jexactyl:jexactyl:4.0.0:rc1:*:*:*:*:*:* Versions 4.0.0 rc1 Vulnerable ·Jexactyl
- cpe:2.3:a:jexactyl:jexactyl:4.0.0:rc2:*:*:*:*:*:* Versions 4.0.0 rc2 Vulnerable ·Jexactyl
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-33061
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences