AnsibleForms: Stored cross-site scripting (job output and form fields)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| ansibleguy76 | ansibleforms | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Ansibleguy76 | Ansibleforms |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.274% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ansibleguy76
Ansibleguy76 ansibleforms |
|
| Vendors & Products |
Ansibleguy76
Ansibleguy76 ansibleforms |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | AnsibleForms is a self-hosted web application that turns automation into self-service forms. Prior to 6.2.1, AnsibleForms stores attacker-influenceable job output that server/src/lib/common.js processes through formatOutput without HTML escaping and client/src/components/AppAnsibleOutput.vue renders through v-html. An authenticated user can submit job input that is echoed into persistent output, causing script execution when another user views the job. Additional designer-controlled HTML and expression values reach v-html in client/src/components/AppForm.vue and client/src/components/BsInputForForm.vue without sanitization. Because Content Security Policy is disabled and the JWT is stored in localStorage, script execution can steal a victim's token and take over the account, including an administrator account. This issue is fixed in version 6.2.1. | |
| Title | AnsibleForms: Stored cross-site scripting (job output and form fields) | |
| Weaknesses | CWE-1021 CWE-79 CWE-922 |
|
| References |
| |
| Metrics |
cvssV3_1
|