OSV 1.4.0 · github-reviewed · 修改于 2026-06-09 19:56
发布时间
2026-05-19 22:44
GitHub 审查时间
2026-05-19 22:44
NVD 发布时间
2026-06-06 03:16
源文件
advisories/github-reviewed/2026/05/GHSA-2m6p-hm3w-6jm3/GHSA-2m6p-hm3w-6jm3.json
A stored cross-site scripting (XSS) vulnerability exists in HAX CMS due to improper sanitization of the <video-player> component.
The component allows javascript: URIs in the source attribute, which are executed when the page is viewed. This enables attackers to execute arbitrary JavaScript in the context of the victim’s browser and access sensitive data such as JWT tokens and more.
The vulnerability is present in the <video-player> web component used within the HAX CMS editor.
The application fails to validate or sanitize user-supplied input in the following attributes:
sourcesource-dataThese attributes accept arbitrary URI schemes, including javascript:, which leads to execution of attacker-controlled JavaScript in the browser.
Example vulnerable usage:
<video-player
source="javascript:alert(document.domain)"
source-type="external">
</video-player>
Because this content is stored and rendered to other users, the vulnerability is classified as a stored XSS.
The root cause is the lack of URI scheme validation and improper sanitization of component attributes before rendering. Because this content is stored and rendered to other users, the vulnerability is classified as a stored XSS.
The root cause is the lack of URI scheme validation and improper sanitization of component attributes before rendering.
Steps to reproduce:
<>).<video-player source="javascript:alert('JWT: '+localStorage.getItem('jwt').substring(0,30))" source-type="external"></video-player>
<img width="2456" height="1405" alt="image" src="https://github.com/user-attachments/assets/ea037043-7ff7-4840-bed0-1091692c6289" />
Save the page.
Reload or revisit or send the page.
Result <img width="2468" height="1394" alt="image" src="https://github.com/user-attachments/assets/543bbf69-900d-4e2d-bd6b-0658fb5aa899" />
A JavaScript alert executes. The JWT token is exposed. This confirms arbitrary JavaScript execution in the victim’s browser.
This vulnerability allows stored XSS leading to:
If an administrator views a malicious page, this can lead to full CMS compromise.
Attack complexity: Low
Privileges required: Low (any authenticated user)
User interaction: Required