CVE-2026-100176

The AIL Framework crawler splash domain page (showDomain.html) is vulnerable to stored cross-site script injection (XSS). User-supplied data from imported crawler captures (item IDs, URLs, and screenshot file paths) is interpolated directly into inline JavaScript contexts without escaping. An attacker with a user-role API client can import a malicious capture, and when any user (including privileged ones) views the domain page, the script executes in the victim's browser.

The Onion module in AIL Framework has a performance shortcut in URL extraction that accepts URLs as valid .onion targets based only on a length check (exactly 69 characters) and a suffix check (ending in '.onion'), without proper hostname parsing. An unauthenticated attacker who can publish or control web content crawled by the framework can embed a crafted URL with an IP address or non-onion hostname that satisfies these conditions and gets queued as a legitimate onion crawler task.

The AIL Framework crawler task creation API (api_add_crawler_task) has an insufficient authorization check when a user supplies a cookiejar UUID. The original code only verified that the cookiejar exists and, if its access level was 0, compared the owner user ID to the requesting user ID. It did not validate organizational boundaries or account for the user's role. An authenticated user can reference another organization's cookiejar and have the crawler use that organization's stored cookies when performing web crawls.

The AIL Framework tag selector component (var/www/static/js/tags.js) is vulnerable to stored XSS. A user with the ability to create custom tags can embed HTML payloads containing JavaScript event handlers in the tag name. When another authenticated user opens a page containing the tag selector, the malicious tag name is inserted into the DOM using jQuery's html property, causing the embedded script to execute.

The AIL Framework contains a stored cross-site scripting (XSS) vulnerability in two Jinja2 templates that render popovers for matched, tracked, or tagged content. Dynamic values are interpolated directly into the data-content attribute without output encoding, and the popovers are configured with data-html="true", allowing injected markup to execute in the victim's session.

The AIL framework contains a path traversal vulnerability in the /objects/item/diff endpoint. This allows an authenticated AIL user to craft malicious item identifiers that may lead to unauthorized disclosure of local files.

AIL Framework contains a server-side request forgery (SSRF) vulnerability in its crawler submission functionality. A low-privileged authenticated user can submit an arbitrary URL for crawling without adequate validation of the destination host. The crawler can be instructed to make requests to internal addresses, including loopback, private networks, and cloud metadata services.

AIL Framework contains a stored cross-site scripting vulnerability in the crawler domain view. Crawled URLs were embedded directly into the JavaScript onclick handler without proper encoding. An attacker can inject malicious JavaScript into a stored URL, which executes in the analyst's browser when the screenshot icon is clicked.

Reflected XSS vulnerability in AIL Framework at the /tag/add_tags endpoint. The error value is returned without proper encoding, allowing arbitrary HTML or JavaScript execution in the victim's browser.

AIL Framework has a path traversal vulnerability in its PDF object handling. The PDF.get_filepath() function constructs a file path by joining the configured PDF storage directory with a PDF object identifier without verifying the resolved path stays within the intended PDF_FOLDER directory. An authenticated attacker can use crafted identifiers with relative traversal sequences or absolute path components to open files outside the PDF directory, potentially disclosing sensitive data.