WordPress More Fields Plugin 2.1 contains a cross-site request forgery vulnerability that allows attackers to perform unauthorized actions by disabling CSRF token validation. Attackers can craft malicious web pages that trick logged-in administrators into adding or deleting custom fields and boxes on the Write/Edit page via POST and GET requests to the options-general.php endpoint.
CVE-2016-20083
Score 5.3 from GitHub Security Advisory published 2026-06-15. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 55(Attend)EG Risk 55/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 3.7%
- KEV
- Not listed
Published
June 15, 2026
Last Modified
June 15, 2026
Advisory Details (3)
Auto-updated Jun 15, 2026WordPress More Fields Plugin 2.1 Cross-Site Request Forgery | Advisories | VulnCheck
https://www.vulncheck.com/advisories/wordpress-more-fields-plugin-cross-site-request-forgeryWordPress Plugin More Fields 2.1 - Cross-Site Request Forgery - PHP webapps Exploit
https://www.exploit-db.com/exploits/39507Vendor Advisories for CVE-2016-20083(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 61× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:14 UTCEPSS rescore
- 2026-07-23 01:22 UTCEG score recompute
- 2026-07-22 22:01 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-20 17:03 UTCEPSS rescore
- 2026-07-19 14:27 UTCEPSS rescore
- 2026-07-18 10:00 UTCEPSS rescore
- 2026-07-18 10:00 UTCEPSS rescore
- 2026-07-17 06:37 UTCGHSA enrichment
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 08:35 UTCGHSA enrichment
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 10:01 UTCGHSA enrichment
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-14 11:56 UTCGHSA enrichment
- 2026-07-13 22:26 UTCEPSS rescore
- 2026-07-13 13:53 UTCGHSA enrichment
- 2026-07-13 06:09 UTCEPSS rescore
- 2026-07-12 15:51 UTCGHSA enrichment
- 2026-07-12 05:43 UTCEPSS rescore
Show 63 moreShow fewer
- 2026-07-12 05:43 UTCEPSS rescore
- 2026-07-11 17:17 UTCGHSA enrichment
- 2026-07-11 08:23 UTCEPSS rescore
- 2026-07-10 19:14 UTCGHSA enrichment
- 2026-07-09 21:12 UTCGHSA enrichment
- 2026-07-09 19:05 UTCEPSS rescore
- 2026-07-08 20:30 UTCGHSA enrichment
- 2026-07-08 15:10 UTCEPSS rescore
- 2026-07-07 22:28 UTCGHSA enrichment
- 2026-07-07 13:42 UTCEPSS rescore
- 2026-07-07 00:26 UTCGHSA enrichment
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-05 21:28 UTCGHSA enrichment
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-04 23:03 UTCGHSA enrichment
- 2026-07-04 06:28 UTCEPSS rescore
- 2026-07-04 01:01 UTCGHSA enrichment
- 2026-07-03 02:48 UTCGHSA enrichment
- 2026-07-02 04:46 UTCGHSA enrichment
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-07-01 06:45 UTCGHSA enrichment
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-30 08:43 UTCGHSA enrichment
- 2026-06-29 14:03 UTCEPSS rescore
- 2026-06-29 10:39 UTCGHSA enrichment
- 2026-06-28 14:04 UTCEPSS rescore
- 2026-06-28 12:34 UTCGHSA enrichment
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-27 14:33 UTCGHSA enrichment
- 2026-06-27 03:05 UTCEPSS rescore
- 2026-06-27 03:05 UTCEPSS rescore
- 2026-06-26 16:31 UTCGHSA enrichment
- 2026-06-25 18:30 UTCGHSA enrichment
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-24 20:28 UTCGHSA enrichment
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-23 22:17 UTCGHSA enrichment
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-22 23:44 UTCGHSA enrichment
- 2026-06-22 14:23 UTCEPSS rescore
- 2026-06-22 01:43 UTCGHSA enrichment
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-21 02:52 UTCGHSA enrichment
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-20 04:33 UTCGHSA enrichment
- 2026-06-19 19:23 UTCEPSS rescore
- 2026-06-19 19:23 UTCEPSS rescore
- 2026-06-19 06:23 UTCGHSA enrichment
- 2026-06-18 17:50 UTCEPSS rescore
- 2026-06-18 08:21 UTCGHSA enrichment
- 2026-06-17 17:50 UTCEPSS rescore
- 2026-06-17 17:50 UTCEPSS rescore
- 2026-06-17 10:12 UTCGHSA enrichment
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-16 12:07 UTCGHSA enrichment
- 2026-06-15 14:04 UTCEG score recompute
- 2026-06-15 14:03 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2016-20083?
When was CVE-2016-20083 disclosed?
Is CVE-2016-20083 actively exploited?
What is the CVSS score of CVE-2016-20083?
How do I remediate CVE-2016-20083?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2016-20083
Is Your Infrastructure Affected by CVE-2016-20083?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.