![]() ![]() ![]() We encourage everyone to get started working with GraphQL v4 today: Start using Silverstripe GraphQL v4 today # We are planning to require the use of silverstripe/graphql:^4 in a future CMS 4.x release. ![]() The resulting silverstripe/graphql:^4 release is currently in an alpha stage. look at the silverstripe/graphql pull requests to see exactly what has changed.review Epic: Scaling decoupled CMS usage (GraphQL performance) to better understand the goals.If you want to learn more about the development of silverstripe/graphql v4: The module was rewritten from scratch with performance in mind. The CMS currently ships with silverstripe/graphql:^3.5, which is stable but slow for larger schemas. To drive various parts of the CMS UI, as well as to build your own GraphQL APIs in your Silverstripe CMS projects. CVE-2020-26138 Validate custom multi-file uploads Severity: Lowįeatures and enhancements # Support for silverstripe/graphql v4 #.CVE-2020-25817 XXE Vulnerability in CSSContentParser Severity: Low.CVE-2020-26136 GraphQL doesn't honour MFA when using basic auth Severity: Medium.You can read the severity rating definitions in the Silverstripe CMS release process. We have provided a high-level severity rating of the vulnerabilities below based on the CVSS score, however please note this could vary based on the specifics of each project. We highly encourage upgrading your project to include the latest security patches nonetheless. Please see the release announcements for more detailedÄescriptions of each. This upgrade can be carried out by any development team familiar with Silverstripe. Upgrading to Recipe 4.8.0 is recommended for all sites. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |