CVE-2021-22951 json
Password exposure in concrete5/core
published 2021-11-19 4 y ago modified 2026-06-17 4 mo ago also GHSA-rhf5-f553-xg82 , EUVD-2021-2391
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
Unauthorized individuals could view password protected files using view_inline in Concrete CMS (previously concrete 5) prior to version 8.5.7. Concrete CMS now checks to see if a file has a password in view_inline and, if it does, the file is not rendered.For version 8.5.6, the following mitigations were put in place a. restricting file types for view_inline to images only b. putting a warning in the file manager to advise users.Credit for discovery: "Solar Security Research Team"Concrete CMS security team CVSS scoring is 5.3: AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NThis fix is also in Concrete version 9.0.0
Patch / fix
- packagist concrete5/core 8.5.7
- concretecms concrete_cms 8.5.7
Exploit prediction
1.11% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).
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:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | concrete5/core | <8.5.7 |
8.5.7 |
Affected products
- n/a https://github.com/concrete5/concrete5
Classification
References
-
documentation.concretecms.org
/developers/introduction/version-history/857-release-notes
web, release-notes, vendor-advisory
-
hackerone.com
/reports/1102014
web, permissions-required, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-22951
advisory
Sources
- CVE List CVE-2021-22951
- GitHub Advisory GHSA-rhf5-f553-xg82
- NVD CVE-2021-22951
Fencer Vulns 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.