Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14116: Server-Side Request Forgery in xerrors Yuxi-Know

0
Medium
VulnerabilityCVE-2025-14116cvecve-2025-14116
Published: Fri Dec 05 2025 (12/05/2025, 22:32:08 UTC)
Source: CVE Database V5
Vendor/Project: xerrors
Product: Yuxi-Know

Description

A vulnerability was detected in xerrors Yuxi-Know up to 0.4.0. This vulnerability affects the function OtherEmbedding.aencode of the file /src/models/embed.py. Performing manipulation of the argument health_url results in server-side request forgery. The attack can be initiated remotely. The exploit is now public and may be used. The patch is named 0ff771dc1933d5a6b78f804115e78a7d8625c3f3. To fix this issue, it is recommended to deploy a patch. The vendor responded with a vulnerability confirmation and a list of security measures they have established already (e.g. disabled URL parsing, disabled URL upload mode, removed URL-to-markdown conversion).

AI-Powered Analysis

AILast updated: 12/05/2025, 23:00:16 UTC

Technical Analysis

CVE-2025-14116 is a Server-Side Request Forgery (SSRF) vulnerability identified in the open-source project xerrors Yuxi-Know, specifically affecting versions 0.1 through 0.4.0. The vulnerability exists in the function OtherEmbedding.aencode located in the file /src/models/embed.py. The flaw stems from insufficient validation and sanitization of the health_url argument, which an attacker can manipulate to induce the server to make arbitrary HTTP requests. This SSRF can be exploited remotely without user interaction but requires the attacker to have high privileges (PR:H) on the system, indicating that some level of authentication or elevated access is necessary to trigger the vulnerability. The impact on confidentiality, integrity, and availability is limited (VC:L, VI:L, VA:L), suggesting that while the attacker can coerce the server to send requests, the potential damage is somewhat constrained. The vendor has acknowledged the vulnerability and responded by disabling URL parsing, disabling URL upload modes, and removing URL-to-markdown conversion features to reduce attack surface. A patch identified by commit 0ff771dc1933d5a6b78f804115e78a7d8625c3f3 is available and recommended for deployment. Although no known exploits are currently in the wild, the public availability of the exploit code increases the risk of future attacks. The vulnerability has a CVSS 4.0 base score of 5.1, categorized as medium severity, reflecting moderate risk due to ease of exploitation and potential impact.

Potential Impact

For European organizations, the SSRF vulnerability in xerrors Yuxi-Know could lead to unauthorized internal network scanning, access to internal services, or exploitation of trust relationships within the network. This can facilitate lateral movement, data exfiltration, or further compromise of internal systems. Organizations using affected versions in critical infrastructure, research, or data-sensitive environments may face increased risk of information leakage or disruption. The requirement for high privileges to exploit limits the threat to insiders or attackers who have already gained elevated access, but the public availability of the exploit code increases the risk of privilege escalation chains. Given the medium severity, the impact is moderate but should not be underestimated, especially in sectors with stringent data protection regulations such as GDPR. Failure to patch could expose organizations to compliance risks and potential reputational damage if internal resources are compromised via SSRF.

Mitigation Recommendations

European organizations should immediately identify and inventory all deployments of xerrors Yuxi-Know versions 0.1 through 0.4.0. The primary mitigation is to apply the vendor-provided patch (commit 0ff771dc1933d5a6b78f804115e78a7d8625c3f3) to eliminate the vulnerability. In addition, organizations should: 1) Restrict and monitor internal network access to limit SSRF exploitation impact; 2) Implement strict input validation and sanitization on any user-controllable parameters, especially URLs; 3) Employ network segmentation to isolate critical services from application servers; 4) Use web application firewalls (WAFs) with SSRF detection rules to detect and block suspicious outbound requests; 5) Conduct regular privilege audits to minimize the number of users with high-level access; 6) Monitor logs for unusual outbound requests or access patterns indicative of SSRF attempts; 7) Disable unnecessary URL parsing or upload features if not required; and 8) Educate developers and administrators about SSRF risks and secure coding practices to prevent similar vulnerabilities in future releases.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-12-05T15:15:26.362Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6933607ff88dbe026c285293

Added to database: 12/5/2025, 10:45:19 PM

Last enriched: 12/5/2025, 11:00:16 PM

Last updated: 12/6/2025, 5:05:09 AM

Views: 34

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats