YesWiki before 4.6.7 contains a server-side request forgery vulnerability that allows unauthenticated attackers to trigger server requests by… (CVE-2026-104463)
YesWiki versions prior to 4.6.7 have a server-side request forgery (SSRF) vulnerability. This flaw allows unauthenticated attackers to send signed Follow activities to a public actor inbox route, causing the server to make unauthorized internal requests. Attackers can use their own keyId to sign these requests while specifying internal actor URLs, potentially accessing internal hosts or cloud metadata services. The vulnerability has a high severity rating with a CVSS score of 7. No explicit patch information is provided in the input data.
AI Analysis
Technical Summary
YesWiki before version 4.6.7 contains a server-side request forgery vulnerability (CVE-2026-104463) that enables unauthenticated attackers to trigger server requests by sending signed Follow activities to the public forms actor inbox route. The attacker signs requests with their own keyId but includes internal actor URLs in the request body. This allows blind GET and POST requests to internal hosts or cloud metadata endpoints, potentially exposing sensitive internal resources.
Potential Impact
The vulnerability allows unauthenticated attackers to cause the YesWiki server to make unauthorized requests to internal network resources or cloud metadata services. This can lead to unauthorized data disclosure (confidentiality impact), partial integrity loss, and availability impact due to the server processing unintended requests. The CVSS score of 7 indicates a high severity impact primarily on confidentiality and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability affects versions before 4.6.7, upgrading to version 4.6.7 or later is likely the intended remediation. Until official guidance is available, restrict access to the affected public forms actor inbox route and monitor for suspicious signed Follow activities.
YesWiki before 4.6.7 contains a server-side request forgery vulnerability that allows unauthenticated attackers to trigger server requests by… (CVE-2026-104463)
Description
YesWiki versions prior to 4.6.7 have a server-side request forgery (SSRF) vulnerability. This flaw allows unauthenticated attackers to send signed Follow activities to a public actor inbox route, causing the server to make unauthorized internal requests. Attackers can use their own keyId to sign these requests while specifying internal actor URLs, potentially accessing internal hosts or cloud metadata services. The vulnerability has a high severity rating with a CVSS score of 7. No explicit patch information is provided in the input data.
CVSS v3.1
Score 7.0high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
YesWiki before version 4.6.7 contains a server-side request forgery vulnerability (CVE-2026-104463) that enables unauthenticated attackers to trigger server requests by sending signed Follow activities to the public forms actor inbox route. The attacker signs requests with their own keyId but includes internal actor URLs in the request body. This allows blind GET and POST requests to internal hosts or cloud metadata endpoints, potentially exposing sensitive internal resources.
Potential Impact
The vulnerability allows unauthenticated attackers to cause the YesWiki server to make unauthorized requests to internal network resources or cloud metadata services. This can lead to unauthorized data disclosure (confidentiality impact), partial integrity loss, and availability impact due to the server processing unintended requests. The CVSS score of 7 indicates a high severity impact primarily on confidentiality and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability affects versions before 4.6.7, upgrading to version 4.6.7 or later is likely the intended remediation. Until official guidance is available, restrict access to the affected public forms actor inbox route and monitor for suspicious signed Follow activities.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9xvr-55wh-mcjh
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-104463"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6abfee8aa43b0b3b89e54bec
Added to database: 10/02/2026, 17:48:58 UTC
Last enriched: 10/02/2026, 17:57:50 UTC
Last updated: 10/02/2026, 21:46:06 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.