CVE-2020-23960 json
Cross-Site Request Forgery in ForkCMS
published 5y ago modified 4mo ago also GHSA-pvgf-mrr4-cw7r , EUVD-2021-1153
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
Multiple cross-site request forgery (CSRF) vulnerabilities in the Admin Console in Fork before 5.8.3 allows remote attackers to perform unauthorized actions as administrator to (1) approve the mass of the user's comments, (2) restoring a deleted user, (3) installing or running modules, (4) resetting the analytics, (5) pinging the mailmotor api, (6) uploading things to the media library, (7) exporting locale.
Patch / fix
- packagist forkcms/forkcms 5.8.3
- fork-cms fork_cms 5.8.3
- github.com/forkcms/forkcms#3123 pull request
Is CVE-2020-23960 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.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | forkcms/forkcms | <5.8.3 |
5.8.3 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/forkcms/forkcms/pull/3123
web, patch, third-party-advisory
-
fork-cms.com
/blog/detail/fork-5.8.3-released
web, release-notes, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-23960
advisory
Sources
- CVE List CVE-2020-23960
- GitHub Advisory GHSA-pvgf-mrr4-cw7r
- NVD CVE-2020-23960
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.