CVE-2020-14961 json
Unrestricted Uploads in Concrete5
published 6y ago modified 4mo ago also GHSA-g4gm-pxh3-29fq , EUVD-2022-0996
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
Concrete5 before 8.5.3 does not constrain the sort direction to a valid asc or desc value.
Patch / fix
- packagist concrete5/concrete5 8.5.3
- concretecms concrete_cms 8.5.3
- github.com/concrete5/concrete5#8651 pull request
- github.com/concrete5/concrete5/releases/tag/8.5.3 release
Is CVE-2020-14961 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
0.97% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | concrete5/concrete5 | <8.5.3 |
8.5.3 |
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
github.com
/concrete5/concrete5/pull/8651
web, patch, third-party-advisory
-
github.com
/concrete5/concrete5/releases/tag/8.5.3
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-14961
advisory
-
github.com
/concrete5/concrete5
package
Sources
- CVE List CVE-2020-14961
- GitHub Advisory GHSA-g4gm-pxh3-29fq
- NVD CVE-2020-14961
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.