changedetection.io: Stored XSS in Watch update via API
A Stored Cross Site Scripting is present in the changedetection.io Watch update API due to unsufficient security checks.
A Stored Cross Site Scripting is present in the changedetection.io Watch update API due to unsufficient security checks.
XSS - Errors in filters from website page change detection watches were not being filtered.
Improper input validation in the application can allow attackers to perform local file read (LFR) or path traversal attacks. These vulnerabilities occur when user input is used to construct file paths without adequate sanitization or validation. For example, using file:../../../etc/passwd or file: ///etc/passwd can bypass weak validations and allow unauthorized access to sensitive files. Even though this has been addressed in previous patch, it is still insufficient.
The validation for the file URI scheme falls short, and results in an attacker being able to read any file on the system. This issue only affects instances with a webdriver enabled, and ALLOW_FILE_URI false or not defined.
When a WebDriver is used to fetch files source:file:///etc/passwd can be used to retrieve local system files, where the more traditional file:///etc/passwd gets blocked
A Server Side Template Injection in changedetection.io caused by usage of unsafe functions of Jinja2 allows Remote Command Execution on the server host.
Input in parameter notification_urls is not processed resulting in javascript execution in the application
API endpoint /api/v1/watch/<uuid>/history can be accessed by any unauthorized user.
Changedetection.io before 0.40.2 was discovered to contain a stored cross-site scripting (XSS) vulnerability in the main page. This vulnerability allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the URL parameter under the "Add a new change detection watch" function.