Quick answers
- Is CVE-2026-104457 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104457 being exploited in the wild.
- How severe is CVE-2026-104457?
- High severity, with a CVSS score of 8.6, published 2 October 2026.
- Which products and versions are affected?
- YesWiki before 4.6.7.
- Is there a fix for CVE-2026-104457?
- Yes: fixed in 4.6.7. Until then: Set default_write_acl to restrict page creation and editing to authenticated users only, preventing unauthenticated attackers from saving malicious filtertags markup on a default install. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104457 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-104457?
- Check whether you run 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
- Fixed in: 4.6.7
Set default_write_acl to restrict page creation and editing to authenticated users only, preventing unauthenticated attackers from saving malicious filtertags markup on a default install.
Technical details
The filtertags action in tools/bazar/actions/filtertags.php concatenates user-supplied filterN parameters directly into a raw SQL tags.value IN (...) clause without proper escaping or parameterization. The _convert() function on UTF-8 MySQL instances is a passthrough and does not escape special characters. An attacker can inject a trailing backslash in a filter token to flip quote parity under MySQL's default sql_mode (with backslash-escapes enabled), allowing injection of a five-column UNION subquery to read arbitrary table data.
Affected products
- YesWiki YesWiki before 4.6.7
Timeline
- 2026-09-01: disclosed
- 2026-10-02: advisory