Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-46670 – Unauthenticated SQL Injection – YesWiki < 4.6.4

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-46670 is a critical, unauthenticated SQL injection vulnerability affecting YesWiki, an open-source wiki platform. The flaw resides in the Bazar form-import functionality (FormManager::create()) and allows any unauthenticated visitor to a default YesWiki install to inject arbitrary SQL and extract the entire database, including user password hashes. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: FormManager::create() performs unquoted concatenation of the bn_id_nature parameter directly into an SQL INSERT VALUES statement without sanitization.
  • Trigger condition: An attacker submits a crafted Bazar form-import request containing SQL expressions (e.g., using ASCII/SUBSTRING/HEX(VERSION())) in place of the expected numeric value.
  • Attack vector: The injected SQL expression is evaluated by the database before being stored, and the resulting inserted ID value leaks query results as numeric data, enabling character-by-character data extraction (a form of error/inference-based blind SQLi).
  • Access requirements: No authentication and no user interaction are required; the vulnerable functionality is reachable by any unauthenticated visitor on a default installation.
  • Impact: Full compromise of the underlying database, including exposure of the yeswiki_users table (usernames, emails, and password hashes), enabling downstream account takeover and further compromise.

Affected software

  • YesWiki versions prior to 4.6.4, including confirmed vulnerable releases 4.6.1 and 4.6.2 (and the corresponding development branch commit).

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade YesWiki to version 4.6.4 or later, which patches the vulnerable SQL construction in FormManager::create().
  • If immediate patching is not possible: Restrict or disable public access to the Bazar form-import functionality, place a web application firewall in front of the instance to filter anomalous numeric/SQL-expression input in form submissions, and monitor database logs for suspicious query patterns.
  • Following the upgrade, rotate credentials for all YesWiki user accounts, particularly administrative accounts, as password hashes may have already been exposed.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Named response header (Link): YesWiki-
  • Raw response body: yeswiki.net

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge