Summary
CVE-2026-85380 is a high-severity server-side request forgery vulnerability in UEditor's catchimage function. A remote attacker may manipulate the source[] parameter to make the server send requests to attacker-selected or otherwise restricted locations when the feature is reachable and insufficiently protected.
Affected context
The issue occurs in the UEditor PHP controller at Public/ueditor/php/controller.php, specifically in the catchimage function. It becomes risky when the endpoint accepts remotely supplied image sources, causes the server to fetch those locations, and does not sufficiently restrict destination schemes, addresses, ports, or network ranges. The rolling-release nature of the project means deployment-specific revision status should be assessed independently.
Exploit preconditions
- Attack surface: A remotely reachable UEditor
catchimageendpoint - Required access: Access sufficient to submit requests to the endpoint; authentication requirements depend on the deployment
- Trigger point: Processing of attacker-influenced values in the
source[]argument - Why exploitation is possible: The server may resolve and request attacker-selected destinations without adequate validation or network egress restrictions
Why this happens
The underlying bug is server-side request forgery, mapped to CWE-918. The application treats user-controlled source locations as fetchable resources without establishing a sufficiently narrow trust boundary around permitted destinations. This insecure pattern allows application-side network operations to be influenced by external input, potentially exposing internal services or other network resources.
Potential impact
- The server may issue requests to internal or otherwise restricted network locations
- Cloud or infrastructure metadata may be exposed where reachable and insufficiently protected
- Internal service information may be disclosed through response behavior, errors, or stored results
- The vulnerability could support reconnaissance or follow-on attacks against accessible services
- Server resources may be consumed through requests to unintended destinations
General mitigation guidance
Mitigation generally focuses on reducing trust in externally supplied URLs and constraining server-side network access.
Common defensive patterns include:
- Allowing only explicitly approved URL schemes, hosts, ports, and destination ranges
- Resolving hostnames and validating final addresses before making requests
- Blocking loopback, link-local, private, reserved, and metadata-service ranges where they are not required
- Applying network egress controls so the application can reach only necessary services
- Avoiding automatic retrieval when a secure upload or trusted object-storage workflow is sufficient
- Enforcing authentication, authorization, rate limits, and request timeouts around image-fetching functionality
- Preventing fetched content from being interpreted as executable or trusted application input
How teams detect issues like this
Detection approaches can include:
- Static analysis for server-side HTTP clients that consume request parameters directly
- Code review checks for URL validation that relies only on string prefixes or initial DNS results
- Tests covering redirects, alternate address representations, private networks, and unexpected schemes
- Web-application monitoring for unusual outbound requests from the UEditor process
- Network policy alerts for application traffic to internal ranges, metadata endpoints, or unapproved external destinations
- Automated security review tools and dependency scanning rules for SSRF-prone request flows

