PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-104467 – Authorization Bypass (Unauthenticated Admin API Access) – 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-104467 is a critical authorization bypass vulnerability (CWE-862: Missing Authorization) affecting YesWiki, an open-source collaborative wiki platform, in all versions prior to 4.6.7. The flaw resides in ApiService::isAuthorized() and allows unauthenticated attackers to invoke admin-only API routes whenever the wiki’s "public API mode" is enabled. It is rated Critical with a CVSS v4.0 base score of 9.2.

Technical details

  • Root cause: ApiService::isAuthorized() grants API access based on the presence of api_allowed_keys => ['public' => true] in the wiki configuration before route-level access control lists (ACLs) are evaluated. The public configuration branch is not restricted to routes whose ACL explicitly permits public access, so it ends up authorizing any matched API route, including ones annotated as admin-only (@admins).
  • Trigger conditions: The target instance must have the documented public API mode enabled ('api_allowed_keys' => ['public' => true] in configuration), and the called controller must not implement a secondary, in-method admin check.
  • Attack vector: Network-based; an unauthenticated attacker sends direct HTTP requests to admin-only API endpoints such as api/ci/update_config and api/archives. No authentication, prior access, or user interaction is required.
  • Impact: Successful exploitation allows an unauthenticated attacker to overwrite arbitrary wiki configuration values, and to list, download, delete, or otherwise manage backup archives. Additional admin-only routes (e.g., custom CSS preset deletion) rely on the same flawed central authorization check.

Affected software

  • YesWiki (yeswiki/yeswiki) — all versions prior to 4.6.7, when public API mode is enabled.
  • Fixed in YesWiki 4.6.7 and later.

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade affected YesWiki instances to version 4.6.7 or later, which corrects the authorization logic in ApiService::isAuthorized().
  • If immediate patching is not possible: Review whether public API mode ('api_allowed_keys' => ['public' => true]) is actually required, and disable it if not in active use. Restrict network access to the wiki’s /api/ endpoints (e.g., via a reverse proxy or firewall rule) until the upgrade can be applied.

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