The wp-d3 plugin before 2.4.1 for WordPress has CSRF.

published 2019-09-13 7 y ago modified 2026-06-17 4 mo ago also EUVD-2016-1937

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

Patch / fix

fixed in 1

wp-d3_project wp-d3 2.4.1

Exploit prediction

0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

wpvulndb.com https://wpvulndb.com/vulnerabilities/8679 referenced PoC, tagged "exploit" by a source, unverified

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

Technology feeds

WordPress rss critical rss

References

wpvulndb.com /vulnerabilities/8679
exploit, third-party-advisory
wordpress.org /plugins/wp-d3/#developers
third-party-advisory

Sources

CVE List CVE-2016-10946
NVD CVE-2016-10946

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.

Summary