T05 · Unauthorized Access and Privilege Escalation
- Location
scripts/form-submit.js:30- Finding
Chromium Runs Without Its Security Sandbox
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill can help automate web forms, but it needs Review because it can reuse login sessions and submit arbitrary forms with weak safeguards.
Install only if you are comfortable with an automation helper that can act inside logged-in web sessions and submit forms. Use it only with session files you treat like passwords, verify the target domain before restoring a session, avoid payments/account changes/legal submissions unless you explicitly intend them, and prefer adding dry-run and confirmation checks before submit.
scripts/form-submit.js:30Chromium Runs Without Its Security Sandbox
scripts/form-submit.js:38Session Storage Is Imported Without Verifying the Destination Origin
The declared description presents a web automation skill centered on interacting with websites and submitting forms. The supplied code chunk does not perform any browser automation or website interaction at all. It only converts a local input image to an output file, apparently intended for webp compression, and reports file sizes. While image compression could be a supporting component of a larger upload workflow, this code chunk by itself does not implement the primary declared functionality and therefore materially differs from the stated purpose.
Referenced artifact was not completely inspected
- `form-submit.js` - Generic form submission template
The activation language is very broad and can cause the skill to trigger for many generic website tasks, including sensitive account actions, uploads, or submissions. In an automation skill that can replay sessions, upload files, and submit forms, over-broad invocation increases the chance of unintended use on high-risk workflows.
Recommending force-click on submit buttons without caution encourages bypassing UI checks that may intentionally prevent invalid, incomplete, or unreviewed submissions. In a form automation context, this can lead to unintended data submission, bypass of user-interface safety interlocks, and actions taken before the page is actually in a valid state.
The skill instructs loading cookies and localStorage/sessionStorage into a browser context without warning that these artifacts may contain bearer tokens, authentication state, and other secrets. This is dangerous because imported session material can enable account takeover-like behavior, cross-account actions, or leakage of sensitive credentials if mishandled.
The script will unconditionally click the configured submit button with force enabled, which can trigger irreversible actions such as account changes, purchases, uploads, or data submission without any final safety check. In a web-form automation skill, this is especially relevant because the explicit purpose is to interact with arbitrary websites, so misuse or operator error can cause real-world side effects immediately.
No suspicious patterns detected.