# CVE-2026-104467: YesWiki authorization bypass in public API mode

Source: https://junglewise.ai/threats/cve-2026-104467-yeswiki-before-4-6-7-contains-an-authorization-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-02. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-104467 · Severity: high · CVSS 8.1 · Published 2026-10-02

YesWiki is a collaborative wiki platform that stores website content and configuration. When public API mode is enabled (a documented feature), unauthenticated attackers can bypass authorization checks and access admin-only functions. This allows attackers to modify configuration, access database backups, delete archives, and change CSS settings without any authentication.

Technologies: [YesWiki](https://junglewise.ai/threats/technologies/yeswiki). Vendors: [YesWiki](https://junglewise.ai/threats/vendors/yeswiki).

## 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

## References

- [https://github.com/YesWiki/yeswiki/security/advisories/GHSA-v527-6r4j-j2w2](https://github.com/YesWiki/yeswiki/security/advisories/GHSA-v527-6r4j-j2w2)
- [https://www.vulncheck.com/advisories/yeswiki-before-4.6.7-authorization-bypass-via-public-api-mode](https://www.vulncheck.com/advisories/yeswiki-before-4.6.7-authorization-bypass-via-public-api-mode)

## Related threats

- [YesWiki SQL injection in despam.php INTERVAL operand](https://junglewise.ai/threats/cve-2026-116828-yeswiki-before-4-7-0-contains-a-sql-injection-vulnerability-in)
- [YesWiki server-side request forgery in Bazar CSV import](https://junglewise.ai/threats/cve-2026-116827-yeswiki-before-4-7-0-contains-a-server-side-request-forgery)
- [YesWiki server-side request forgery in DuplicationManager](https://junglewise.ai/threats/cve-2026-116826-yeswiki-before-4-7-0-contains-a-server-side-request-forgery)
- [YesWiki HTTP Signature replay protection missing in ActivityPub inbox](https://junglewise.ai/threats/cve-2026-116825-yeswiki-from-4-6-2-before-4-7-0-lacks-replay-protection-in)
- [YesWiki stored cross-site scripting in referrers_sites handler](https://junglewise.ai/threats/cve-2026-116824-yeswiki-before-4-7-0-contains-a-stored-cross-site-scripting)