CVE-2016-20070

MEDIUMPre-NVD 6.46.4
EchelonGraph scoreHIGH confidence

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

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

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

WordPress Booking Calendar Contact Form 1.0.23 contains privilege escalation and stored cross-site scripting vulnerabilities that allow authenticated users to modify plugin options and inject malicious scripts by failing to verify user privileges and sanitize input parameters. Attackers with subscriber-level accounts can inject XSS payloads through parameters like price, name, calendar_language, and email_confirmation_to_user via admin-ajax.php and admin.php endpoints to execute arbitrary JavaScript in administrator browsers.

CVSS v3
6.4
EG Score
6.4(high)
EPSS
13.9%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 15, 2026

Advisory Details (2)

Auto-updated Jun 15, 2026
No patch confirmed yet.
generic

WordPress Booking Calendar Contact Form 1.0.23 Privilege Escalation Stored XSS | Advisories | VulnCheck

https://www.vulncheck.com/advisories/wordpress-booking-calendar-contact-form-privilege-escalation-stored-xss
generic

Boost your WordPress - Plugins for WordPress

http://wordpress.dwbooster.com/

Vendor Advisories for CVE-2016-20070(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 19× in last 7d / 69× 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:27 UTCEG score recompute
  2. 2026-07-07 00:27 UTCGHSA enrichment
  3. 2026-07-06 16:24 UTCEPSS rescore
  4. 2026-07-06 16:24 UTCEPSS rescore
  5. 2026-07-06 02:20 UTCEPSS rescore
  6. 2026-07-06 02:20 UTCEPSS rescore
  7. 2026-07-05 11:50 UTCEG score recompute
  8. 2026-07-05 11:49 UTCGHSA enrichment
  9. 2026-07-05 02:27 UTCEPSS rescore
  10. 2026-07-04 10:06 UTCEG score recompute
  11. 2026-07-04 10:06 UTCGHSA enrichment
  12. 2026-07-04 06:28 UTCEPSS rescore
  13. 2026-07-03 00:29 UTCEG score recompute
  14. 2026-07-03 00:29 UTCGHSA enrichment
  15. 2026-07-01 22:44 UTCEG score recompute
  16. 2026-07-01 22:44 UTCGHSA enrichment
  17. 2026-07-01 15:02 UTCEPSS rescore
  18. 2026-06-30 20:19 UTCEG score recompute
  19. 2026-06-30 20:19 UTCGHSA enrichment
  20. 2026-06-29 18:36 UTCEG score recompute
  21. 2026-06-29 18:36 UTCGHSA enrichment
  22. 2026-06-29 14:03 UTCEPSS rescore
  23. 2026-06-28 15:25 UTCEG score recompute
  24. 2026-06-28 15:25 UTCGHSA enrichment
  25. 2026-06-28 14:04 UTCEPSS rescore
Show 44 more
  1. 2026-06-28 04:53 UTCEPSS rescore
  2. 2026-06-27 13:42 UTCEG score recompute
  3. 2026-06-27 13:42 UTCGHSA enrichment
  4. 2026-06-27 03:05 UTCEPSS rescore
  5. 2026-06-27 03:05 UTCEPSS rescore
  6. 2026-06-26 11:58 UTCEG score recompute
  7. 2026-06-26 11:58 UTCGHSA enrichment
  8. 2026-06-25 13:47 UTCEPSS rescore
  9. 2026-06-25 13:47 UTCEPSS rescore
  10. 2026-06-25 08:28 UTCEG score recompute
  11. 2026-06-25 08:28 UTCGHSA enrichment
  12. 2026-06-24 14:02 UTCEPSS rescore
  13. 2026-06-24 14:02 UTCEPSS rescore
  14. 2026-06-24 06:45 UTCEG score recompute
  15. 2026-06-24 06:45 UTCGHSA enrichment
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-23 04:04 UTCEG score recompute
  18. 2026-06-23 04:04 UTCGHSA enrichment
  19. 2026-06-22 14:23 UTCEPSS rescore
  20. 2026-06-22 01:43 UTCEG score recompute
  21. 2026-06-22 01:43 UTCGHSA enrichment
  22. 2026-06-21 14:54 UTCEPSS rescore
  23. 2026-06-21 14:54 UTCEPSS rescore
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
  26. 2026-06-20 22:45 UTCEG score recompute
  27. 2026-06-20 22:45 UTCGHSA enrichment
  28. 2026-06-19 20:58 UTCEG score recompute
  29. 2026-06-19 20:58 UTCGHSA enrichment
  30. 2026-06-19 19:23 UTCEPSS rescore
  31. 2026-06-19 19:23 UTCEPSS rescore
  32. 2026-06-18 19:16 UTCEG score recompute
  33. 2026-06-18 19:16 UTCGHSA enrichment
  34. 2026-06-18 17:50 UTCEPSS rescore
  35. 2026-06-17 17:50 UTCEPSS rescore
  36. 2026-06-17 17:50 UTCEPSS rescore
  37. 2026-06-17 17:32 UTCEG score recompute
  38. 2026-06-17 17:31 UTCGHSA enrichment
  39. 2026-06-16 17:50 UTCEPSS rescore
  40. 2026-06-16 17:50 UTCEPSS rescore
  41. 2026-06-16 15:48 UTCEG score recompute
  42. 2026-06-16 15:48 UTCGHSA enrichment
  43. 2026-06-15 14:06 UTCEG score recompute
  44. 2026-06-15 14:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2016-20070?
CVE-2016-20070 is a medium vulnerability published on June 15, 2026. WordPress Booking Calendar Contact Form 1.0.23 contains privilege escalation and stored cross-site scripting vulnerabilities that allow authenticated users to modify plugin options and inject malicious scripts by failing to verify user privileges and sanitize input parameters. Attackers with…
When was CVE-2016-20070 disclosed?
CVE-2016-20070 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-20070 actively exploited?
CVE-2016-20070 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-20070?
CVE-2016-20070 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2016-20070?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-20070, 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-20070

Explore →

Is Your Infrastructure Affected by CVE-2016-20070?

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