CVE-2020-27665 json
Improper Authorization in Strapi
published 6y ago modified 4mo ago also GHSA-4p55-xj37-fx7g , EUVD-2020-1407
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
In Strapi before 3.2.5, there is no admin::hasPermissions restriction for CTB (aka content-type-builder) routes.
Patch / fix
- npm strapi-plugin-content-type-builder 3.2.5
- strapi strapi 3.2.5
- github.com/strapi/strapi@3cdd739 commit
- github.com/strapi/strapi#8439 pull request
- github.com/strapi/strapi/releases/tag/v3.2.5 release
Is CVE-2020-27665 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | strapi-plugin-content-type-builder | <3.2.5 |
3.2.5 |
Classification
- Weakness
-
- CWE-276 Incorrect Default Permissions
References
-
github.com
/strapi/strapi/pull/8439
web, patch, third-party-advisory
-
github.com
/strapi/strapi/commit/3cdd73987950d5c7976701047b38203e902007bb
web
-
github.com
/strapi/strapi/releases/tag/v3.2.5
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-27665
advisory
-
snyk.io
/vuln/SNYK-JS-STRAPIPLUGINCONTENTTYPEBUILDER-1021616
web
Sources
- CVE List CVE-2020-27665
- GitHub Advisory GHSA-4p55-xj37-fx7g
- NVD CVE-2020-27665
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.