GHSA-2vc4-3hx7-v7v7

Hax CMS Stored Cross-Site Scripting vulnerability

### Summary The application does not sufficiently sanitize user input, allowing for the execution of arbitrary JavaScript code. The 'saveNode' and 'saveManifest' endpoints take user input and store it in the JSON schema for the site. This content is then rendered in the generated HAX site. Although the application does not allow users to supply a 'script' tag, it does allow the use of other HTML tags to run JavaScript. ### Affected Resources - [Operations.php:258](https://github.com/haxtheweb/haxcms-php/blob/master/system/backend/php/lib/Operations.php#L258) `saveManifest()` - [Operations.php:868](https://github.com/haxtheweb/haxcms-php/blob/master/system/backend/php/lib/Operations.php#L868) `saveNode()` - `https://<site>/<user>/system/api/saveNode` - `https://<site>/<user>/system/api/saveManifest` ### Impact An authenticated attacker can use the site editor and settings editor to store malicious payloads in a HAX site which execute arbitrary JavaScript when a user visits the site. This can be used to steal a user's session cookie or other sensitive data. ### PoCs #### saveNode To replicate this vulnerability, an attacker can use the "View Source" functionality within the site editor to enter a malicious payload. 1. Select "View Source" within the HAX site editor and enter an XSS payload that does not use the "script" HTML tag.  3. Select "Update HTML" and observe the resulting alert.   #### saveManifest To exploit the 'SaveManifest' endpoint, an attacker can insert executable code into the URL field of the site settings editor: any payload added this way will execute when the site is loaded. 1. Open the site settings editor.  3. Add JavaScript code to the URL field under the "Theme" header.  5. Reload the page to run the script.  7. The resulting page source will contain the script.