edx-platform before 2016-06-06 allows CSRF.

published 2019-07-29 7y ago modified 2026-06-17 4mo ago also EUVD-2016-1760

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 49%
public exploits: 0; none known

Patch / fix

fixed in 1 links 1

edx edx-platform 2016-06-06

github.com/edx/edx-platform@d54f79f commit

Is CVE-2016-10766 in your stack? 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.60% chance of exploitation in the next 30 days, higher than 49% 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

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

github.com /edx/edx-platform/commit/d54f79f5bf3e1af17063937df1abc0026843412d.patch
patch, third-party-advisory
open.edx.org /announcements/cross-site-request-forgery-bug-edx-lms/
vendor-advisory

Sources

CVE List CVE-2016-10766
NVD CVE-2016-10766

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.