Quick answers
- Is CVE-2026-46670 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46670 being exploited in the wild.
- How severe is CVE-2026-46670?
- Critical severity, with a CVSS score of 9.8, published 11 August 2026.
- Which products and versions are affected?
- yeswiki/yeswiki (Packagist) < 4.6.4, ECOSYSTEM:introduced=0,fixed=4.6.4; YesWiki < 4.6.4.
- Is there a fix for CVE-2026-46670?
- Yes. yeswiki/yeswiki (Packagist): upgrade to 4.6.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-46670 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-46670?
- Check whether you run yeswiki/yeswiki (Packagist) or YesWiki at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- yeswiki/yeswiki (Packagist): upgrade to 4.6.4 or later
composer require yeswiki/yeswiki:^4.6.4
Technical details
An unauthenticated SQL injection vulnerability exists in YesWiki's Bazar form-import component, specifically within the FormManager::create() function. The root cause is the unquoted concatenation of the 'bn_id_nature' parameter into an SQL INSERT statement. An attacker can exploit this by sending a specially crafted POST request to the Bazar form-import path, allowing them to inject arbitrary SQL. This can be used to perform blind SQL injection to exfiltrate sensitive data, such as user credentials and email addresses, from the database. The vulnerability is patched in version 4.6.4.
Affected products
- YesWiki YesWiki < 4.6.4
Identifiers
- CVE-2026-46670
- GHSA-jwvv-qr7q-cv8j
Timeline
- 2026-05-22: advisory: GitHub Advisory GHSA-jwvv-qr7q-cv8j published.
- 2026-05-22: patched: Fix released in version 4.6.4.