CVE-2016-20083

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-06-15. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(high)
EPSS
3.6%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 15, 2026

Advisory Details (3)

Auto-updated Jun 15, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

WordPress More Fields Plugin 2.1 Cross-Site Request Forgery | Advisories | VulnCheck

https://www.vulncheck.com/advisories/wordpress-more-fields-plugin-cross-site-request-forgery
generic🟡 PoC Available

WordPress Plugin More Fields 2.1 - Cross-Site Request Forgery - PHP webapps Exploit

https://www.exploit-db.com/exploits/39507
generic

[More Fields] Support | WordPress.org

https://wordpress.org/support/plugin/more-fields

Vendor 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 22× in last 7d / 76× 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.

  1. 2026-07-07 00:26 UTCEG score recompute
  2. 2026-07-07 00:26 UTCGHSA enrichment
  3. 2026-07-06 16:24 UTCEPSS rescore
  4. 2026-07-06 16:24 UTCEPSS rescore
  5. 2026-07-05 21:28 UTCEG score recompute
  6. 2026-07-05 21:28 UTCGHSA enrichment
  7. 2026-07-05 02:27 UTCEPSS rescore
  8. 2026-07-04 23:03 UTCEG score recompute
  9. 2026-07-04 23:03 UTCGHSA enrichment
  10. 2026-07-04 06:28 UTCEPSS rescore
  11. 2026-07-04 01:01 UTCEG score recompute
  12. 2026-07-04 01:01 UTCGHSA enrichment
  13. 2026-07-03 02:48 UTCEG score recompute
  14. 2026-07-03 02:48 UTCGHSA enrichment
  15. 2026-07-02 04:46 UTCEG score recompute
  16. 2026-07-02 04:46 UTCGHSA enrichment
  17. 2026-07-01 15:02 UTCEPSS rescore
  18. 2026-07-01 06:45 UTCEG score recompute
  19. 2026-07-01 06:45 UTCGHSA enrichment
  20. 2026-06-30 23:19 UTCEPSS rescore
  21. 2026-06-30 08:43 UTCEG score recompute
  22. 2026-06-30 08:43 UTCGHSA enrichment
  23. 2026-06-29 14:03 UTCEPSS rescore
  24. 2026-06-29 10:39 UTCEG score recompute
  25. 2026-06-29 10:39 UTCGHSA enrichment
Show 51 more
  1. 2026-06-28 14:04 UTCEPSS rescore
  2. 2026-06-28 12:34 UTCEG score recompute
  3. 2026-06-28 12:34 UTCGHSA enrichment
  4. 2026-06-28 04:53 UTCEPSS rescore
  5. 2026-06-27 14:33 UTCEG score recompute
  6. 2026-06-27 14:33 UTCGHSA enrichment
  7. 2026-06-27 03:05 UTCEPSS rescore
  8. 2026-06-27 03:05 UTCEPSS rescore
  9. 2026-06-26 16:31 UTCEG score recompute
  10. 2026-06-26 16:31 UTCGHSA enrichment
  11. 2026-06-25 18:30 UTCEG score recompute
  12. 2026-06-25 18:30 UTCGHSA enrichment
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-24 20:28 UTCEG score recompute
  16. 2026-06-24 20:28 UTCGHSA enrichment
  17. 2026-06-24 14:02 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-23 22:17 UTCEG score recompute
  20. 2026-06-23 22:17 UTCGHSA enrichment
  21. 2026-06-23 21:30 UTCEPSS rescore
  22. 2026-06-22 23:44 UTCEG score recompute
  23. 2026-06-22 23:44 UTCGHSA enrichment
  24. 2026-06-22 14:23 UTCEPSS rescore
  25. 2026-06-22 01:43 UTCEG score recompute
  26. 2026-06-22 01:43 UTCGHSA enrichment
  27. 2026-06-21 14:54 UTCEPSS rescore
  28. 2026-06-21 14:54 UTCEPSS rescore
  29. 2026-06-21 02:52 UTCEG score recompute
  30. 2026-06-21 02:52 UTCGHSA enrichment
  31. 2026-06-21 01:57 UTCEPSS rescore
  32. 2026-06-21 01:57 UTCEPSS rescore
  33. 2026-06-20 04:33 UTCEG score recompute
  34. 2026-06-20 04:33 UTCGHSA enrichment
  35. 2026-06-19 19:23 UTCEPSS rescore
  36. 2026-06-19 19:23 UTCEPSS rescore
  37. 2026-06-19 06:23 UTCEG score recompute
  38. 2026-06-19 06:23 UTCGHSA enrichment
  39. 2026-06-18 17:50 UTCEPSS rescore
  40. 2026-06-18 08:21 UTCEG score recompute
  41. 2026-06-18 08:21 UTCGHSA enrichment
  42. 2026-06-17 17:50 UTCEPSS rescore
  43. 2026-06-17 17:50 UTCEPSS rescore
  44. 2026-06-17 10:13 UTCEG score recompute
  45. 2026-06-17 10:12 UTCGHSA enrichment
  46. 2026-06-16 17:50 UTCEPSS rescore
  47. 2026-06-16 17:50 UTCEPSS rescore
  48. 2026-06-16 12:07 UTCEG score recompute
  49. 2026-06-16 12:07 UTCGHSA enrichment
  50. 2026-06-15 14:04 UTCEG score recompute
  51. 2026-06-15 14:03 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2016-20083?
CVE-2016-20083 is a medium vulnerability published on June 15, 2026. 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…
When was CVE-2016-20083 disclosed?
CVE-2016-20083 was first published in the National Vulnerability Database on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-20083 actively exploited?
CVE-2016-20083 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-20083?
CVE-2016-20083 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2016-20083?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-20083, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-20083

Explore →

Is Your Infrastructure Affected by CVE-2016-20083?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs