Argilla
Monthly
Stored cross-site scripting in Argilla's annotation text field component (argilla-frontend/components/features/annotation/container/fields/text-field/TextField.vue) allows a user who can write annotation text to persist markup that executes in another user's browser session when the poisoned record is viewed. The assessed vector requires an authenticated principal with privileges to submit or edit annotation text plus interaction from a second viewer, with impact limited to low integrity and no confidentiality or availability loss; all Argilla branches from 2.0 through 2.8.0 are listed as affected. A public proof-of-concept reference exists but is not verified as working exploit code, EPSS is 0.21% (11th percentile), and the vulnerability is not in CISA KEV - priority guidance is to monitor rather than act urgently.
Stored cross-site scripting in Argilla 2.0 through 2.8.0 allows a privileged, authenticated user to inject a crafted value into the 'template' argument of a custom annotation field, which is rendered by argilla-frontend/components/features/annotation/container/fields/sandbox/Sandbox.vue and executes in the browser of a second user who later views that field. The assessed CVSS:3.1 vector (AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N) confines the outcome to limited integrity impact in the victim's browser session, with no confidentiality or availability impact, and the high-privilege prerequisite plus the need for a victim to open the crafted annotation are the main limiting factors. This is a low-priority, low-risk issue: EPSS is 0.21% (11th percentile), there is no CISA KEV entry, the priority decision is 'monitor', and a public PoC reference exists but is not verified as working exploit code. No vendor fix has been identified; the project was notified via issue #5876 and has not responded.
Stored cross-site scripting in Argilla 2.0 through 2.8.0 allows a user who can create or edit a dataset to inject script into the dataset Name field, which then executes in the browser of another user who opens that dataset's Settings page (SettingsInfo.vue). Because the injection point is the dataset name, an attacker needs an authenticated account with dataset-creation privileges (PR:L) and the victim must actually load the affected settings view (UI:P), which keeps the practical impact narrow; the CVSS 4.0 score is 2.0 and EPSS is only 0.25% (17th percentile), so the vulnerability is tracked as monitor priority. No vendor patch exists at time of analysis - Argilla was notified through GitHub issue #5875 and has not responded - and a public PoC reference exists; it is not verified as working exploit code.
Stored cross-site scripting in Argilla's annotation text field component (argilla-frontend/components/features/annotation/container/fields/text-field/TextField.vue) allows a user who can write annotation text to persist markup that executes in another user's browser session when the poisoned record is viewed. The assessed vector requires an authenticated principal with privileges to submit or edit annotation text plus interaction from a second viewer, with impact limited to low integrity and no confidentiality or availability loss; all Argilla branches from 2.0 through 2.8.0 are listed as affected. A public proof-of-concept reference exists but is not verified as working exploit code, EPSS is 0.21% (11th percentile), and the vulnerability is not in CISA KEV - priority guidance is to monitor rather than act urgently.
Stored cross-site scripting in Argilla 2.0 through 2.8.0 allows a privileged, authenticated user to inject a crafted value into the 'template' argument of a custom annotation field, which is rendered by argilla-frontend/components/features/annotation/container/fields/sandbox/Sandbox.vue and executes in the browser of a second user who later views that field. The assessed CVSS:3.1 vector (AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N) confines the outcome to limited integrity impact in the victim's browser session, with no confidentiality or availability impact, and the high-privilege prerequisite plus the need for a victim to open the crafted annotation are the main limiting factors. This is a low-priority, low-risk issue: EPSS is 0.21% (11th percentile), there is no CISA KEV entry, the priority decision is 'monitor', and a public PoC reference exists but is not verified as working exploit code. No vendor fix has been identified; the project was notified via issue #5876 and has not responded.
Stored cross-site scripting in Argilla 2.0 through 2.8.0 allows a user who can create or edit a dataset to inject script into the dataset Name field, which then executes in the browser of another user who opens that dataset's Settings page (SettingsInfo.vue). Because the injection point is the dataset name, an attacker needs an authenticated account with dataset-creation privileges (PR:L) and the victim must actually load the affected settings view (UI:P), which keeps the practical impact narrow; the CVSS 4.0 score is 2.0 and EPSS is only 0.25% (17th percentile), so the vulnerability is tracked as monitor priority. No vendor patch exists at time of analysis - Argilla was notified through GitHub issue #5875 and has not responded - and a public PoC reference exists; it is not verified as working exploit code.