# CVE-2023-36472: @strapi/plugin-content — Fixed in 4.11.7 📦 📦 npm Not in CISA KEV MEDIUM severity # CVE-2023-36472 — @strapi/plugin-content-ma… MEDIUM CVE-2023-36472 is a medium-severity (CVSS 5.8) Information Exposure vulnerability in @strapi/plugin-content-manager. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for @strapi/plugin-content-manager — see the affected versions and patch details below. Strapi may leak sensitive user information, user reset password, tokens via content-manager views Also known as[GHSA-v8gg-4mq2-88q4](/vulnerability/GHSA-v8gg-4mq2-88q4) Published Sep 15, 2023 Updated Oct 28, 2026 Affected 3 pkgs Patched 3 / 3 Exploits 1 known Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### Proof-of-concept exploit code exists - CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation. Exploitation and automatability from CISA’s SSVC triage for CVE-2023-36472. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.7%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk 0.00%0.39%0.78%1.17%0.1%0.7%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really ## Where this sits among everything scored ## Real-World Exposure 3 pkgs affected How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched. 20other npm packages depend on this — each one inherits the vulnerability until it's patched upstream `@strapi/plugin-content-manager`npm 50Kdownloads / week `@strapi/admin`npm 316Kdownloads / week `@strapi/utils`npm 485Kdownloads / week ## Description #### Summary I can get access to user reset password tokens if I have the configure view permissions ![b37a6fd9eae06027e7d91266f1908a3d](https://user-images.githubusercontent.com/34578426/246782921-fbc007d3-ffec-45de-a1f1-a4287cd507ac.png) ![6c1da5b3bfbb3bca97c8d064be0ecb05](https://user-images.githubusercontent.com/34578426/246783044-7d716dde-6f27-4d01-9521-42720c6ce92e.gif) #### Details /content-manager/relations route does not remove private fields or ensure that they can't be selected #### PoC Install fresh strapi instance start up strapi and create an account create a new content-type give the content-type a relation with admin users and save go to Admin panel roles Author and then plugins. Enable for content-manager collection types the configure view In the collection time now only give them access to the collection you created for this. Create a new admin user account with the Author role Log out and request a password reset for the main admin user. Login on the newly created account go to the collection type you created for this test and click the create new entry button, click in the create new entry view on configure view. select the admin user relation we created click on resetPasswordToken Now go back to the create an entry view and when selection the relation we created we now see the reset tokken #### Impact Impact is that the none admin user now has the reset token of the admin users account and can resets its password using that to escalate his privilege's Still you need the configure view permission to be able to escalate your privilege's ## Affected Packages 3 total 3 fixed Ecosystem Package Vulnerable range Fix 📦npm `@strapi/plugin-content-manager` all versions 4.11.7`npm install @strapi/plugin-content-manager@4.11.7` 📦npm `@strapi/admin` all versions 4.11.7`npm install @strapi/admin@4.11.7` 📦npm `@strapi/utils` all versions 4.11.7`npm install @strapi/utils@4.11.7` ## Affected Products 1 product · 1 configurations Application `strapi`strapi < 4.11.7 range Exploits & PoCs 1 Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization. [ Strapi is an open-source headless content management system. Prior to ve… github.comNVDSep 2023 ](https://github.com/strapi/strapi/security/advisories/GHSA-v8gg-4mq2-88q4) ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @strapi/plugin-content-manager, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update @strapi/plugin-content-manager to 4.11.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-36472 is resolved across your whole dependency graph. 3. ### Workarounds Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them. ## Frequently Asked Questions \### Summary I can get access to user reset password tokens if I have the configure view permissions !\[b37a6fd9eae06027e7d91266f1908a3d\](https://user-images.githubusercontent.com/34578426/246782921-fbc007d3-ffec-45de-a1f1-a4287cd507ac.png) !\[6c1da5b3bfbb3bca97c8d064be0ecb05\](https://user-images.githubusercontent.com/34578426/246783044-7d716dde-6f27-4d01-9521-42720c6ce92e.gif) ### Details /content-manager/relations route does not remove private fields or ensure that they can't be selected ### PoC Install fresh strapi instance start up strapi and create an account create a new content-type giv O3 Security · Impact-Aware SCA ### Is CVE-2023-36472 in your dependencies? Find it across npm, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)