CVE-2026-46670

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.7%, top 25% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

YesWiki is a wiki system written in PHP. Prior to version 4.6.4, an unauthenticated SQL injection in the Bazar form-import path (FormManager::create()) allows any unauthenticated visitor of a default YesWiki install to inject arbitrary SQL into an INSERT statement and read the full database, including yeswiki_users.password hashes. Version 4.6.4 fixes the issue.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/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 computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
2%
EPSS %ILE
75%
KEV
Not listed

Published

May 22, 2026

Last Modified

August 13, 2026

Advisory Details (1)

Auto-updated Aug 20, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Unauthenticated SQL Injection · Advisory · YesWiki/yeswiki · GitHub

https://github.com/YesWiki/yeswiki/security/advisories/GHSA-jwvv-qr7q-cv8j

Vendor Advisories for CVE-2026-46670(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
yeswiki/yeswiki4.2.3 ... v4.6.3 (29 versions)4.6.4

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 27× 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-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-23 16:41 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-22 01:40 UTCEG score recompute
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 21:41 UTCEG score recompute
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 18:39 UTCEG score recompute
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 16:48 UTCEG score recompute
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 03:20 UTCEG score recompute
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 01:57 UTCEG score recompute
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 01:53 UTCEG score recompute
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 15:29 UTCEG score recompute
  22. 2026-08-13 14:26 UTCEG score recompute
  23. 2026-08-12 14:13 UTCEG score recompute
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-11 14:25 UTCEG score recompute
Show 7 more
  1. 2026-08-01 17:14 UTCEG score recompute
  2. 2026-07-29 17:30 UTCEG score recompute
  3. 2026-07-23 03:17 UTCEG score recompute
  4. 2026-06-14 23:18 UTCEPSS rescore
  5. 2026-06-13 23:00 UTCEPSS rescore
  6. 2026-06-12 23:12 UTCEPSS rescore
  7. 2026-05-24 06:09 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-46670.yaml
    First seen Jan 1, 2026

    YesWiki < 4.6.4 - Unauthenticated SQL Injection

    Open source ↗

Frequently asked(5)

What is CVE-2026-46670?
CVE-2026-46670 is a critical vulnerability published on May 22, 2026. YesWiki is a wiki system written in PHP. Prior to version 4.6.4, an unauthenticated SQL injection in the Bazar form-import path (FormManager::create()) allows any unauthenticated visitor of a default YesWiki install to inject arbitrary SQL into an INSERT statement and read the full database,…
When was CVE-2026-46670 disclosed?
CVE-2026-46670 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46670 actively exploited?
CVE-2026-46670 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 25.2% of all scored CVEs.
What is the CVSS score of CVE-2026-46670?
CVE-2026-46670 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-46670?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46670, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46670

Explore →

Is Your Infrastructure Affected by CVE-2026-46670?

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