Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Product Based Web Vulnerabilities·Updated Nov 9, 2026

CVE-2026-116205 Scanner

CVE-2026-116205 Scanner - Server-Side-Request-Forgery (SSRF) vulnerability in YesWiki

Est. Time~1 minutes
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
5
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
6.9
CVSSmedium
Exploitable remotely over the internet · no authentication required.
Description

YesWiki before 4.7.0 contains an unauthenticated server-side request forgery vulnerability that allows remote attackers to fetch arbitrary URLs by supplying [[|URL]] wiki syntax to the render handler. Attackers can pass the syntax in the content parameter of the page render handler to reach internal hosts and ports and read their responses.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
yeswikiby YesWiki
AFFECTED< 4.7.0→SAFE ✓≥ 4.7.0
Updated Nov 6, 2026View on NVD →
Detail

YesWiki, a collaborative platform for sharing and managing knowledge, is utilized by various organizations and communities for creating wikis and shared resources. Built as an open-source software, it enables users to create customizable and community-driven websites. This platform is frequently updated to enhance its functionalities and security features, catering to a diverse user base requiring collaborative content management. However, security vulnerabilities can arise with widespread usage, making it necessary for users to update regularly to maintain security. The identified version of YesWiki facilitates potential misuse through improper configurations, highlighting the importance of vigilance in software maintenance. Organizations utilizing YesWiki should monitor for updates to ensure their system integrity and security.

The vulnerability identified in YesWiki 4.7.0 involves an unauthenticated SSRF, where improper handling of URL syntax can lead to unauthorized data access. SSRF vulnerabilities can be exploited by remote attackers to make requests from the vulnerable server, posing significant security risks. This lack of authentication allows attackers to conduct SSRF attacks without needing valid credentials, thereby widening the threat landscape. YesWiki's vulnerability can compromise internal networks and sensitive information if left unpatched. It is crucial to address these vulnerabilities promptly to prevent unauthorized data access. Security assessments and immediate updates are recommended to mitigate potential threats associated with this vulnerability.

Technical details of the vulnerability reveal that YesWiki fails to manage URL handling in the render handler properly. This flaw enables attackers to manipulate the URL syntax, thereby making unauthorized requests through the vulnerable server. Attackers can fetch arbitrary URLs, exposing sensitive internal network data and resources. YesWiki versions below 4.7.0 are affected due to inadequate validation of URL input, allowing exploitation of the SSRF vulnerability. It requires no authentication and exploits the wiki page's content rendering functionality. Employing interactsh, an attacker can confirm the SSRF by examining the server's response to crafted requests.

Exploiting this SSRF vulnerability could lead to unauthorized access to internal systems and sensitive data exposure. It enables attackers to bypass network restrictions, potentially leading to further attacks within compromised environments. Sensitive information such as confidential documents, internal server functions, or restricted network configurations might be accessed or disclosed. If an attacker gains access to sensitive endpoints, it could lead to severe data breaches or facilitate further intrusion attacks. The ripple effect of exploiting the SSRF could compromise system integrity and trust, necessitating immediate patching and security measure implementations.

REFERENCES

Solution Advice
  • Update YesWiki to version 4.7.0 or later to address SSRF vulnerabilities.
  • Regularly monitor and apply security patches for server and application software.
  • Implement network segmentation to reduce exposure of internal resources.
  • Conduct regular security assessments and penetration tests.
  • Consider using web application firewalls (WAF) to detect and prevent SSRF attempts.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.