Approved changes feed: RSS · Atom

cpe:2.3:a:marmelab:ra-ui-materialui:*:*:*:*:*:node.js:*:*

part: a version: * update: *

VendorMarmelab (83499799-d329-533c-b9f9-912f83db4a63)
ProductRa Ui Materialui (34fc1e4a-eb2a-52c4-855f-1550ffe2ea4b)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/mui/material-ui purl2cpe 2026-06-01 10:11:07.203564
pkg:github/mui/material-ui-docs purl2cpe 2026-06-01 10:11:07.203566
pkg:github/mui/material-ui-pickers purl2cpe 2026-06-01 10:11:07.203568

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-25572 vulnerable 2026-06-08 05:56:09.274396 React-Admin vulnerable to Cross-Site-Scripting attack on `<RichTextField>`
MEDIUM (5.4)
react-admin is a frontend framework for building browser applications on top of REST/GraphQL APIs. react-admin prior to versions 3.19.12 and 4.7.6, along with ra-ui-materialui prior to 3.19.12 and 4.7.6, are vulnerable to cross-site scripting. All React applications built with react-admin and using the `<RichTextField>` are affected. `<RichTextField>` outputs the field value using `dangerouslySetInnerHTML` without client-side sanitization. If the data isn't sanitized server-side, this opens a possible cross-site scripting (XSS) attack. Versions 3.19.12 and 4.7.6 now use `DOMPurify` to escape the HTML before outputting it with React and `dangerouslySetInnerHTML`. Users who already sanitize HTML data server-side do not need to upgrade. As a workaround, users may replace the `<RichTextField>` by a custom field doing sanitization by hand.
Published: 2023-02-13T20:49:54.340Z
Updated: 2025-03-10T21:12:31.239Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.