Strapi may leak sensitive user information, user reset password, tokens via content-manager views
strapi
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @strapi/plugin-content-manager npm |
|
|
| @strapi/admin npm |
|
|
| @strapi/utils npm |
strapi
| Product | Affected | Fixed in |
|---|---|---|
| @strapi/plugin-content-manager npm |
|
|
| @strapi/admin npm |
|
|
| @strapi/utils npm |
< 4.11.7
|
Strapi is an open-source headless content management system. Prior to version 4.11.7, an unauthorized actor can get access to user reset password tokens if they have the configure view permissions. The `/content-manager/relations` route does not remove private fields or ensure that they can't be selected. This issue is fixed in version 4.11.7.
From the CVE record · GitHub_M
Before 4.11.7, Strapi’s `/content-manager/relations` route does not remove private fields or prevent them from being selected. An actor with configure view permissions can access user reset password tokens through this route.
Teams running Strapi with @strapi/plugin-content-manager, @strapi/admin, or @strapi/utils versions earlier than 4.11.7 should check their installations.