Security readout for executives and security teams
Plain-English summary
YesWiki versions before 4.6.4 contain a critical database injection flaw reachable without authentication. An internet visitor could access or alter sensitive database content, including stored user password hashes, and potentially disrupt service. Public-facing default installations are the highest priority.
Executive priority
Treat this as an immediate remediation item. Upgrade exposed systems first, preserve relevant logs, and initiate compromise assessment. Because password hashes may be disclosed and database contents altered, potentially affected systems warrant credential and data-integrity review even without confirmed active exploitation.
Technical view
The Bazar form-import path passes attacker-controlled input through FormManager::create() into an INSERT statement, enabling unauthenticated SQL injection. The CVSS 3.1 score is 9.8 because exploitation requires no privileges or user interaction and may severely affect confidentiality, integrity, and availability. CWE-89 applies.
Likely exposure
YesWiki installations running versions earlier than 4.6.4 are affected. Exposure is greatest when the vulnerable Bazar form-import functionality is reachable from untrusted networks. The supplied sources specifically describe default installations as remotely accessible to unauthenticated visitors.
Exploitation context
The vulnerability is remotely reachable, low complexity, and requires neither authentication nor user interaction. It can disclose the full database, including yeswiki_users.password hashes. The supplied bundle reports no CISA KEV listing and provides no evidence of active exploitation in the wild.
Researcher notes
The source bundle identifies the vulnerable sink as an INSERT statement reached through Bazar form import and FormManager::create(). It does not provide evidence of exploitation in the wild, detailed indicators of compromise, affected configuration exceptions, or mitigations beyond upgrading. Validate those details against current vendor guidance.
Mitigation direction
- Upgrade YesWiki to version 4.6.4 or later.
- Prioritize internet-facing and default-configured installations.
- Restrict untrusted access to affected YesWiki instances until upgraded.
- Review vendor guidance for any additional remediation or compromise indicators.
- Require password resets if investigation indicates password hashes were accessed.
Validation and detection
- Inventory deployed YesWiki versions and identify every instance below 4.6.4.
- Confirm whether affected instances are reachable from the internet or other untrusted networks.
- Verify the deployed application reports version 4.6.4 or later after upgrading.
- Review database and application logs for unusual form-import activity or unexpected queries.
- Assess database integrity and investigate possible disclosure of stored password hashes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-46670 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/YesWiki/yeswiki/security/advisories/GHSA-jwvv-qr7q-cv8jCVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.