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

New CVE Detected

CVE-2026-104445 – Authentication Bypass (Federated Entry Deletion/Overwrite) – YesWiki before 4.6.7

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

Summary

CVE-2026-104445 is an authentication bypass vulnerability (CWE-290) in YesWiki’s ActivityPub inbox implementation, affecting all versions prior to 4.6.7. The flaw lets any unauthenticated attacker who controls an ActivityPub keypair delete or overwrite federated wiki entries belonging to other actors. The issue carries a CVSS v3.1 base score of 8.2 (High) and a CVSS v4.0 base score of 8.8 (High), and requires no authentication or user interaction to exploit remotely.

Technical details

  • Root cause: YesWiki’s ActivityPub inbox correctly verifies the cryptographic HTTP signature on an incoming activity, but never binds the verified signer identity to the actor claimed inside the activity body — the two are checked independently and never compared.
  • Trigger conditions: An attacker sends a validly signed Delete or Update ActivityPub activity to the inbox endpoint, referencing a mirrored entry’s sourceUrl. Because the signer-to-actor binding is never enforced, the activity is processed as if it came from the entry’s legitimate owner.
  • Attack vector: Network — the inbox endpoint is reachable without any YesWiki account or administrative privileges. The attacker only needs any valid ActivityPub keypair, not one belonging to the targeted actor.
  • Impact: Unauthenticated deletion or overwrite of other actors’ federated/mirrored wiki entries, resulting in a high integrity impact and a lower-severity availability impact, with no confidentiality impact.

Affected software

  • YesWiki, all versions prior to 4.6.7
  • Fixed in YesWiki 4.6.7

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade all YesWiki installations to version 4.6.7 or later, which binds the verified HTTP signature signer to the claimed activity actor before processing Delete/Update operations.
  • If patching is not immediately possible: Restrict or disable public access to the ActivityPub inbox endpoint at the network or reverse-proxy layer until the upgrade can be applied, and monitor for unexpected deletions or overwrites of federated/mirrored entries as an indicator of attempted exploitation.

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