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-14516: Server-Side Request Forgery in Yalantis uCrop

0
Medium
VulnerabilityCVE-2025-14516cvecve-2025-14516
Published: Thu Dec 11 2025 (12/11/2025, 14:02:07 UTC)
Source: CVE Database V5
Vendor/Project: Yalantis
Product: uCrop

Description

A vulnerability was found in Yalantis uCrop 2.2.11. Affected by this issue is the function downloadFile of the file com.yalantis.ucrop.task.BitmapLoadTask.java of the component URL Handler. Performing manipulation results in server-side request forgery. The attack may be initiated remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 12/11/2025, 14:24:11 UTC

Technical Analysis

CVE-2025-14516 is a Server-Side Request Forgery (SSRF) vulnerability identified in the Yalantis uCrop library version 2.2.11, specifically within the downloadFile function of the BitmapLoadTask.java component responsible for URL handling. SSRF vulnerabilities occur when an attacker can manipulate a server-side application to make HTTP requests to arbitrary domains or internal network resources. In this case, the vulnerability allows remote attackers to craft malicious URLs that the vulnerable function processes, causing the server to send requests to unintended destinations. This can lead to unauthorized internal network scanning, access to internal services, or even data exfiltration if the server accesses sensitive endpoints. The vulnerability requires low privileges (PR:L) but no user interaction (UI:N), making it easier to exploit remotely. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no authentication required (AT:N), and partial impacts on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). The vendor was notified but has not responded, and no official patches or mitigations have been released, increasing the risk of exploitation once proof-of-concept code is available publicly. The vulnerability affects only version 2.2.11 of uCrop, a popular Android image cropping library used in various mobile applications. Given the nature of SSRF, attackers could leverage this flaw to bypass firewalls, access internal APIs, or perform further attacks within the victim's network environment.

Potential Impact

For European organizations, the SSRF vulnerability in uCrop 2.2.11 can have several impacts. Organizations embedding this library in their mobile applications or backend services risk unauthorized internal network reconnaissance, potentially exposing sensitive internal services or data. Attackers could exploit this to pivot into internal systems, leading to data breaches or service disruptions. The vulnerability's partial impact on confidentiality, integrity, and availability means attackers might access sensitive information, alter data, or cause denial of service conditions. Since uCrop is widely used in mobile apps, companies in sectors like finance, healthcare, and government could face increased risk if their apps incorporate the vulnerable version. Additionally, the lack of vendor response and patches means organizations must rely on their own mitigations, increasing operational burden. The medium severity suggests that while immediate catastrophic damage is unlikely, the vulnerability can serve as an entry point for more severe attacks, especially in complex enterprise environments.

Mitigation Recommendations

To mitigate CVE-2025-14516, European organizations should first identify all applications and services using Yalantis uCrop version 2.2.11. Since no official patch is available, developers should consider upgrading to a later, unaffected version once released or replacing the library with alternative image cropping solutions. In the interim, implement strict input validation and sanitization on all URLs processed by the downloadFile function to prevent malicious URL injection. Network-level controls should be enforced to restrict outbound HTTP requests from application servers to only trusted destinations, using firewall rules or proxy filtering. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with SSRF detection capabilities to monitor and block suspicious requests. Additionally, segment internal networks to limit the impact of any SSRF exploitation and monitor logs for unusual outbound traffic patterns. Educate development teams about secure coding practices related to URL handling and SSRF risks. Finally, maintain an incident response plan to quickly address any exploitation attempts.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-12-11T06:45:53.170Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 693ad0797d4c6f31f7b1f559

Added to database: 12/11/2025, 2:08:57 PM

Last enriched: 12/11/2025, 2:24:11 PM

Last updated: 12/11/2025, 9:12:15 PM

Views: 12

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