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

New CVE Detected

CVE-2026-104463 – Unauthenticated SSRF – YesWiki before 4.6.7

Be the first to know when new zero-days emerge:

Summary

CVE-2026-104463 is an unauthenticated server-side request forgery (SSRF) vulnerability in YesWiki, a collaborative wiki/CMS platform. The flaw resides in YesWiki’s ActivityPub implementation and allows an unauthenticated remote attacker to force the server to issue arbitrary outbound HTTP GET and POST requests. The issue affects all YesWiki versions prior to 4.6.7 and carries a high severity rating.

Technical details

  • Root cause: The ActivityPub inbox controller (tools/bazar/controllers/ApiController.php) exposes a public POST route that processes "Follow" activities sent to a Bazar form’s actor inbox. While the route verifies the HTTP Signature tied to the request’s keyId, it does not validate the attacker-controlled actor and to URLs contained in the JSON activity body.
  • Trigger conditions: An attacker needs a signed request from their own legitimate ActivityPub actor (which passes signature verification) but can set the actor/to fields to arbitrary URLs. At least one Bazar form with ActivityPub enabled must exist on the target; such forms are discoverable via the public GET /api/forms endpoint.
  • Attack vector: Network, no authentication or user interaction required.
  • Impact: The server can be coerced into making blind GET/POST requests to attacker-chosen destinations, including internal-only hosts/services and cloud instance metadata endpoints (e.g., 169.254.169.254), potentially exposing internal network topology, credentials, or cloud metadata, and enabling further internal reconnaissance or pivoting.

Affected software

  • YesWiki, all versions prior to 4.6.7

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade YesWiki to version 4.6.7 or later, which addresses this SSRF issue.
  • If immediate patching is not possible:
    • Disable ActivityPub functionality on Bazar forms if it is not required.
    • Restrict or firewall outbound requests from the YesWiki server to internal network ranges and cloud metadata addresses.
    • Audit and restrict public exposure of Bazar forms that have ActivityPub enabled.
    • Monitor outbound traffic from the YesWiki host for unexpected requests to internal IP ranges or metadata endpoints.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

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

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge