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

Back
New CVE Detected

CVE-2026-104457 – SQL Injection – YesWiki before 4.6.7

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-104457 is a SQL injection vulnerability in YesWiki, an open-source wiki engine, affecting versions before 4.6.7. The flaw resides in the Bazar filtertags action, where unescaped filterN attribute tokens are concatenated directly into a raw SQL IN (...) clause, allowing unauthenticated attackers on default installations to read arbitrary database contents, including user password hashes. The issue carries a CVSS v3.1 base score of 8.6 (High) and a CVSS v4.0 score of 8.8 (High).

Technical details

  • Root cause: The filtertags action wraps filterN parameter values in quotes and concatenates them into a raw tags.value IN (...) SQL clause without proper escaping or parameterization.
  • Trigger condition: An attacker saves filtertags markup containing a filter token with a trailing backslash (e.g., filter1="x,) union select password,2,3,4,5 from yeswiki_users#"). On MySQL with default backslash-escaping behavior, the trailing backslash breaks quote parity, allowing a UNION-based subquery to be injected.
  • Attack vector: Network-based, requiring no authentication on default YesWiki installations where default_write_acl is set to '*' (anonymous write access). On installations where write access is restricted, exploitation requires page-write privileges.
  • Impact: High confidentiality impact (arbitrary database table data disclosure, including password hashes), with low integrity and availability impact from potential data manipulation or query-induced disruption.

Affected software

  • YesWiki versions prior to 4.6.7 (all versions, per vendor advisory and CVE record)
  • Fixed in YesWiki 4.6.7

Severity

  • CVSS v3.1 Base Score: 8.6 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
  • CVSS v4.0 Base Score: 8.8 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade YesWiki to version 4.6.7 or later, which addresses this SQL injection flaw.
  • If patching is not immediately possible:
    • Restrict anonymous write access by disabling the default '*' write ACL so unauthenticated visitors cannot save filtertags markup.
    • Audit existing wiki pages for suspicious filtertags markup containing trailing backslashes or union select constructs, and remove any identified.
    • Consider placing a web application firewall in front of the installation to filter requests containing SQL UNION/injection patterns in Bazar filter parameters.

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