CVE-2018-25442
Baidu UEditor 1.4.0 before 1.4.3.1 contains a server-side request forgery vulnerability that allows unauthenticated attackers to make arbitr
CVSS
8.3
High
EPSS
—
KEV
—
Exploit Today
—
0-100
Published: Nov 18, 2026 · Last modified: Nov 18, 2026 · CWE-918
Not enough EPSS history yet.
Baidu UEditor 1.4.0 before 1.4.3.1 contains a server-side request forgery vulnerability that allows unauthenticated attackers to make arbitrary requests via the source[] parameter in /ueditor/jsp/controller.jsp?action=catchimage. Attackers can supply crafted URLs that the ImageHunter component fetches through url.openConnection() to reach internal services and bypass network restrictions. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-07-03.
- github.comhttps://github.com/fex-team/ueditor/blob/v1.4.3/jsp/src/com/baidu/ueditor/hunter/ImageHunter.java
- github.comhttps://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/ueditor/ueditor-ssrf.yaml
- www.seebug.orghttps://www.seebug.org/vuldb/ssvid-97311
- www.vulncheck.comhttps://www.vulncheck.com/advisories/baidu-ueditor-1.4.0-1.4.3.1-ssrf-via-controller-jsp-catchimage
- www.vulncheck.comhttps://www.vulncheck.com/advisories/baidu-ueditor-1.4.0-before-1.4.3.1-ssrf-via-controller-jsp-catchimage
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-1317984.3 MED—
———Tanium addressed a server-side request forgery vulnerability.5hCVE-2026-1075188.7 HIG—
———Dell PowerStore contains a Server-Side Request Forgery (SSRF) vulnerability. An authenticated user with limited privileges could potentially exploit this vulnerability to make the appliance connect to attacker-chosen internal systems.1hCVE-2026-829516.1 MED—
——0Latvijas Valsts radio un televīzijas centrs (LVRTC)
eParakstītājs 3.0 version 1.10.0-resolute allows an unauthenticated remote
attacker to cause HTTP GET requests from a user's workstation by convincing the
user to open a crafted signed eDOC file. Automatic certificate validation
retrieves a signer-controlled Authority Information Access (AIA) caIssuers URL
and follows redirects without restricting the destination, enabling blind SSRF
to loopback and private-network services. Additionally, unrestricted loading of
local file URIs (such as file:///dev/zero) causes unbounded memory buffering
resulting in Denial of Service (OutOfMemoryError). In automated server
verification pipelines with UI:N, impact scales up to CVSS 8.6 High.7hCVE-2026-1307248.5 HIG—
——0NocoDB before 2026.08.0 contains a server-side request forgery vulnerability that allows authenticated base Editors to make backend HTTP requests by supplying arbitrary URLs to the integration remote fetch operation. Attackers can control the method, headers, and body to reach internal APIs, loopback services, and cloud metadata endpoints, reading responses and echoed decrypted integration secrets.5hCVE-2026-120406.4 MED—
——0The FS Poster - WordPress Social media Auto Poster & Scheduler [Facebook, Instagram, Twitter, Pinterest] plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 8.0.1 via the 'site_url' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. The Guzzle HTTP client is instantiated with TLS certificate verification disabled and redirect following enabled by default, allowing redirect-based SSRF bypasses and enabling internal port scanning via distinguishable server responses.4hCVE-2026-131820——
——0A server-side request forgery vulnerability in GitHub Enterprise Server allowed an authenticated user with repository write access to send requests to internal services through Slack webhook validity checks, potentially leading to remote code execution on the appliance. Exploitation required Secret Protection with secret scanning and validity checks for partner patterns enabled. This vulnerability affected all versions prior to 3.23 and was fixed in versions 3.22.5, 3.21.10, and 3.20.12. This vulnerability was reported via the GitHub Bug Bounty program.59m