Quick answers
- Is CVE-2026-104467 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104467 being exploited in the wild.
- How severe is CVE-2026-104467?
- High severity, with a CVSS score of 8.1, published 2 October 2026.
- Which products and versions are affected?
- YesWiki before 4.6.7.
- Is there a fix for CVE-2026-104467?
- Yes: fixed in 4.6.7. Until then: Disable public API mode by removing or setting 'api_allowed_keys' => ['public' => true] from configuration until upgrading. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104467 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-104467?
- 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
Disable public API mode by removing or setting 'api_allowed_keys' => ['public' => true] from configuration until upgrading.
Technical details
An authorization bypass flaw in ApiService::isAuthorized() permits unauthenticated API calls to routes marked with @admins ACL when public API mode is configured with 'api_allowed_keys' => ['public' => true]. The check grants access based on the public mode flag without validating that the specific route ACL includes public access, bypassing controller-level authorization. Affected endpoints include /api/ci/update_config (configuration mutation), /api/archives/* (backup management), and /api/templates/custom-presets/* (CSS deletion).
Affected products
- YesWiki YesWiki before 4.6.7
Timeline
- 2026-09-01: disclosed
- 2026-10-02: advisory