Cross-Site Request Forgery in forkcms

published 2021-05-06 5y ago modified 2026-06-17 4mo ago also GHSA-82xf-8h9p-c6qj , EUVD-2021-1287

cvss: 8.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits: 0; none known

Cross-site request forgery (CSRF) in Fork-CMS before 5.8.2 allow remote attackers to hijack the authentication of logged administrators.

Patch / fix

fixed in 2 links 1

packagist forkcms/forkcms 5.8.2
fork-cms fork_cms 5.8.2

github.com/forkcms/forkcms#3123 pull request

Is CVE-2020-23264 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 Fencer

Exploit prediction

0.63% chance of exploitation in the next 30 days, higher than 50% 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.2	5.8.2

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

github.com /forkcms/forkcms/pull/3123
web, issue-tracking, patch, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2020-23264
advisory

Sources

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.