CVE-2026-16070

LOWPre-NVD 2.72.7—
EchelonGraph scoreHIGH confidence

Score 2.7 from GitHub Security Advisory (severity: LOW) published 2026-08-04. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 2.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
2.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.7Exploit: None knownExposed: 0

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

The Brizy WordPress plugin before 2.8.19 does not properly verify authorization on the object being modified before updating a template's type meta, validating a request parameter that is different from the one used in the write operation, allowing users with Contributor-level access and above to change the template-type assignment of templates owned by other users.

CVSS v3
2.7
EG Score
2.7(high)
EG Risk
12(Track)
EG Risk 12/100SSVC: Track

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 computed
Severity27% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 4, 2026

References (1)

Vendor Advisories for CVE-2026-16070(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 11× in last 7d / 30× 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-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 19:35 UTCEG score recompute
  4. 2026-08-17 19:35 UTCGHSA enrichment
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-14 11:56 UTCEG score recompute
  10. 2026-08-14 11:56 UTCGHSA enrichment
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-12 13:50 UTCEPSS rescore
  13. 2026-08-11 13:42 UTCEPSS rescore
  14. 2026-08-11 05:04 UTCEG score recompute
  15. 2026-08-11 05:04 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-09 13:46 UTCEPSS rescore
  18. 2026-08-07 22:12 UTCEG score recompute
  19. 2026-08-07 22:12 UTCGHSA enrichment
  20. 2026-08-06 13:46 UTCEPSS rescore
  21. 2026-08-05 19:17 UTCEPSS rescore
  22. 2026-08-04 15:20 UTCEG score recompute
  23. 2026-08-04 15:20 UTCGHSA enrichment
  24. 2026-08-04 15:10 UTCEPSS rescore
  25. 2026-08-04 14:48 UTCEG score recompute▲ 2.70
Show 5 more
  1. 2026-08-04 14:48 UTCGHSA enrichment
  2. 2026-08-04 14:47 UTCMITRE cvelistV5CVSS v3 → 2.7 · severity → LOW
  3. 2026-08-04 07:17 UTCNVD update
  4. 2026-08-04 06:35 UTCEG score recompute
  5. 2026-08-04 06:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16070?
CVE-2026-16070 is a low vulnerability published on August 4, 2026. The Brizy WordPress plugin before 2.8.19 does not properly verify authorization on the object being modified before updating a template's type meta, validating a request parameter that is different from the one used in the write operation, allowing users with Contributor-level access and above to…
When was CVE-2026-16070 disclosed?
CVE-2026-16070 was first published in the National Vulnerability Database on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16070 actively exploited?
CVE-2026-16070 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.4% of all scored CVEs.
What is the CVSS score of CVE-2026-16070?
CVE-2026-16070 has a CVSS v3.1 base score of 2.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-16070?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16070, 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-2026-16070

Explore →

Is Your Infrastructure Affected by CVE-2026-16070?

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

Start Free Scan →Browse All CVEs