Nuclei is a vulnerability scanner built on a simple YAML-based DSL. From 3.0.0 until 3.10.0, the nuclei/mysql JavaScript library does not enforce the local-file sandbox when a JavaScript template supplies the allowAllFiles MySQL DSN option. An untrusted javascript: template scanning an attacker-controlled MySQL-compatible endpoint can cause the server to issue LOAD DATA LOCAL INFILE requests for arbitrary paths, after which the scanner's MySQL client reads the files and returns their contents to the server even though -allow-local-file-access is disabled. JavaScript templates can run unsigned and without the -code flag on affected versions, and the bypass affects CLI and SDK deployments that accept untrusted templates. This issue is fixed in version 3.10.0.

Affected: Go: github.com/projectdiscovery/nuclei/v3

A vulnerability in Nuclei's JavaScript MySQL client library allows arbitrary local file reads that bypass the `-allow-local-file-access` (`-lfa`) sandbox restriction.

**Affected Component**

The issue is in the `nuclei/mysql` JavaScript library used by `javascript:` protocol templates. The MySQL client connection logic did not enforce the local file access sandbox when handling the `allowAllFiles` DSN parameter used by `LOAD DATA LOCAL INFILE`.

**Description**

Without `-lfa`, Nuclei confines local file access to the templates directory. However, a `javascript:` template could connect to a MySQL server with `allowAllFiles=true` in the connection DSN. With this option enabled, a malicious MySQL server can issue `LOAD DATA LOCAL INFILE` requests for arbitrary paths on the scanner host. The MySQL client reads the full file contents and sends them to the server, bypassing the same sandbox that blocks direct filesystem reads through other APIs.

`javascript:` templates execute without the `-code` flag and unsigned `javascript:` templates run by default, making this reachable from untrusted third-party templates when scanning attacker-controlled MySQL endpoints.

> [!NOTE] The `-allow-local-file-access` (`-lfa`) option is off by default. This issue allows bypassing that restriction, not merely expanding an already-enabled capability.

**Affected Users**

- **CLI users** running untrusted or third-party `javascript:` templates against MySQL-compatible targets. - **SDK users** who…