NocoBase Rich Text Field Stored Cross-Site Scripting via API
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| nocobase | nocobase | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Nocobase | Nocobase |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.298% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | NocoBase fails to sanitize rich text field values in the read renderer, allowing users with create permissions to store malicious HTML with event handlers. Attackers can write arbitrary markup through the collection API that executes in the browsers of all users viewing the affected record. | |
| Title | NocoBase Rich Text Field Stored Cross-Site Scripting via API | |
| First Time appeared |
Nocobase
Nocobase nocobase |
|
| Weaknesses | CWE-79 | |
| CPEs | cpe:2.3:a:nocobase:nocobase:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Nocobase
Nocobase nocobase |
|
| References |
|
|
| Metrics |
cvssV3_1
|