CVE-2026-16058

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-08-19. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

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

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

The YayCurrency WordPress plugin before 3.3.5 does not perform any capability or ownership check on several of its multi-vendor integration handlers that are reachable by unauthenticated users, allowing anyone to read the store's order totals and its vendors' earnings, balance ledgers, and withdrawal histories by iterating identifiers.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
39(Track)
EG Risk 39/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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 19, 2026

Advisory Details (1)

Auto-updated Aug 19, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

YayCurrency < 3.3.5 – Unauthenticated Order and Vendor Financial Data Disclosure via Dokan Integration | CVE 2026-16058 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/d32d7086-9a43-4d98-80d7-18a3f82797bb/

Vendor Advisories for CVE-2026-16058(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 / 11× 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-20 22:55 UTCEPSS rescore
  2. 2026-08-20 14:47 UTCEG score recompute
  3. 2026-08-20 14:47 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 14:26 UTCGHSA enrichment
  6. 2026-08-19 13:38 UTCEG score recompute▲ 5.30
  7. 2026-08-19 13:38 UTCGHSA enrichment
  8. 2026-08-19 13:37 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
  9. 2026-08-19 06:21 UTCNVD update
  10. 2026-08-19 06:18 UTCEG score recompute
  11. 2026-08-19 06:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16058?
CVE-2026-16058 is a medium vulnerability published on August 19, 2026. The YayCurrency WordPress plugin before 3.3.5 does not perform any capability or ownership check on several of its multi-vendor integration handlers that are reachable by unauthenticated users, allowing anyone to read the store's order totals and its vendors' earnings, balance ledgers, and…
When was CVE-2026-16058 disclosed?
CVE-2026-16058 was first published in the National Vulnerability Database on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16058 actively exploited?
CVE-2026-16058 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 85.3% of all scored CVEs.
What is the CVSS score of CVE-2026-16058?
CVE-2026-16058 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-16058?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16058, 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-16058

Explore →

Is Your Infrastructure Affected by CVE-2026-16058?

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

Start Free Scan →Browse All CVEs