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

Back
New CVE Detected

CVE-2026-104464 – SSRF (Unauthenticated) – 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-104464 is a Server-Side Request Forgery (SSRF) vulnerability in YesWiki, a PHP-based collaborative wiki platform. The flaw resides in the Bazar extension’s "abonnements" sync action, which accepts an attacker-controlled actor URL and fetches it from the server without validation. The vulnerability is rated High severity (CVSS 8.8) and is exploitable by unauthenticated remote attackers.

Technical details

  • Root cause: the BazarAction routing for ?vue=abonnements&action=sync&actor=<url> passes the actor parameter directly into ActivityPubService::syncActorPosts(), which issues a GET request to the supplied URI with no scheme restriction or IP-range (e.g., loopback/link-local) blocking.
  • This code path lacks the access-control, CSRF, and hibernation checks applied to other Bazar actions, and an earlier SSRF fix that added URL validation in HttpSignatureService.php does not cover this flow.
  • fetchAllOutboxItems() additionally follows attacker-influenced first/next pagination links returned in the fetched JSON for up to 20 pages, allowing chained/second-order SSRF requests.
  • Attack vector: a single unauthenticated HTTP GET request to any publicly reachable page containing a Bazar component, with the actor parameter pointed at an internal address or cloud metadata endpoint (e.g., http://169.254.169.254/latest/meta-data/).
  • Impact: the server can be coerced into making requests to internal network services or cloud instance metadata services; the fetched response content is stored and exposed as a readable Bazar entry, enabling exfiltration of internal data such as cloud credentials or internal service responses.

Affected software

  • YesWiki (Composer package yeswiki/yeswiki) — all versions up to and including 4.6.6
  • Fixed in version 4.6.7

Severity

  • CVSS v3.1 Base Score: 8.8 (High)
  • Vector: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L (network-exploitable, low complexity, no privileges or user interaction required, high confidentiality impact)

Mitigation and recommended actions

  • Immediate: Upgrade YesWiki to version 4.6.7 or later, where this SSRF path is addressed.
  • If upgrading is not immediately possible: restrict or disable public access to the Bazar "abonnements" sync action (block requests containing vue=abonnements&action=sync at a reverse proxy or WAF), and apply egress filtering/network segmentation so the application server cannot reach internal management interfaces or cloud metadata endpoints (e.g., block outbound access to 169.254.169.254).
  • Review Bazar entries for unexpected content that may indicate the vulnerability was already exploited to exfiltrate internal data.

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