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-10765: Server-Side Request Forgery in SeriaWei ZKEACMS

0
Medium
VulnerabilityCVE-2025-10765cvecve-2025-10765
Published: Sun Sep 21 2025 (09/21/2025, 06:32:06 UTC)
Source: CVE Database V5
Vendor/Project: SeriaWei
Product: ZKEACMS

Description

A security flaw has been discovered in SeriaWei ZKEACMS up to 4.3. This vulnerability affects the function CheckPage/Suggestions in the library cms-v4.3\wwwroot\Plugins\ZKEACMS.SEOSuggestions\ZKEACMS.SEOSuggestions.dll of the component SEOSuggestions. Performing manipulation results in server-side request forgery. It is possible to initiate the attack remotely. The exploit has been released to the public and may be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 09/29/2025, 00:45:40 UTC

Technical Analysis

CVE-2025-10765 is a Server-Side Request Forgery (SSRF) vulnerability identified in SeriaWei's ZKEACMS product, specifically affecting versions 4.0 through 4.3. The vulnerability resides in the CheckPage/Suggestions function within the SEOSuggestions component, implemented in the ZKEACMS.SEOSuggestions.dll library. SSRF vulnerabilities allow an attacker to manipulate server-side requests, causing the server to send crafted HTTP requests to internal or external resources that the attacker normally cannot access. In this case, the flaw can be exploited remotely without user interaction or authentication, as indicated by the CVSS vector. The vulnerability has a CVSS 4.0 base score of 5.1, categorized as medium severity. The attack complexity is low, and no privileges or user interaction are required, but the vulnerability requires high privileges on the system (PR:H), suggesting that the attacker must have some elevated access to exploit it. The impact on confidentiality, integrity, and availability is low, indicating limited damage potential if exploited. The vendor was notified but has not responded or released a patch, and no official fixes are currently available. Although no known exploits are reported in the wild, the public availability of exploit code increases the risk of exploitation. SSRF can be leveraged to access internal services, bypass firewalls, or perform reconnaissance within the victim's network, potentially leading to further attacks if combined with other vulnerabilities or misconfigurations.

Potential Impact

For European organizations using ZKEACMS versions 4.0 to 4.3, this SSRF vulnerability poses a moderate risk. While the direct impact on confidentiality, integrity, and availability is assessed as low, the ability to coerce the server into making arbitrary requests can facilitate lateral movement, internal network reconnaissance, or access to sensitive internal endpoints. This is particularly concerning for organizations hosting sensitive data or critical infrastructure behind the CMS. The lack of vendor response and patches increases exposure time, raising the likelihood of exploitation attempts. European entities relying on ZKEACMS for web content management, especially in sectors such as government, finance, healthcare, or critical infrastructure, may face increased risk if attackers leverage this SSRF to pivot into internal systems or exfiltrate data. The medium severity rating suggests that while immediate catastrophic damage is unlikely, the vulnerability could be a stepping stone for more severe attacks if combined with other weaknesses.

Mitigation Recommendations

Given the absence of official patches, European organizations should implement the following specific mitigations: 1) Restrict network egress from the ZKEACMS server to only necessary external endpoints using firewall rules or network segmentation to limit SSRF exploitation scope. 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious request patterns targeting the SEOSuggestions plugin endpoints. 3) Conduct thorough input validation and sanitization on parameters passed to the CheckPage/Suggestions function, if source code or plugin customization is possible. 4) Monitor logs for unusual outbound requests originating from the CMS server, especially to internal IP ranges or unexpected external domains. 5) Isolate the CMS environment from sensitive internal networks to prevent SSRF from reaching critical systems. 6) Engage in active threat hunting for signs of SSRF exploitation attempts. 7) Plan for an upgrade or migration away from affected ZKEACMS versions once a patch or vendor response becomes available. 8) If feasible, disable or remove the SEOSuggestions plugin until a fix is provided to eliminate the vulnerable attack surface.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-09-20T08:47:44.418Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68d0935fb68a0c387d42a925

Added to database: 9/22/2025, 12:07:59 AM

Last enriched: 9/29/2025, 12:45:40 AM

Last updated: 11/4/2025, 1:39:51 PM

Views: 41

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