Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach catchimage endpoint over network
-
DeliverySubmit URL targeting loopback/link-local address
-
ExploitBypass private-IP validation filter
-
ExecutionServer probes internal HTTP service
-
ImpactInfer internal service state from response differences
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires reaching the Feehi CMS UEditor 'catchimage' endpoint (the server-side image-fetch feature of the bundled UEditor rich-text editor) and supplying an attacker-controlled URL whose host resolves to a loopback (e.g. 127.0.0.1) or link-local (e.g. 169.254.169.254) address - addresses the product's private-IP validation routine fails to block. Meaningful results also require internal HTTP services whose responses differ observably, since the SSRF is semi-blind (inferred via 'response differences') rather than returning full response bodies. Limiting factors: the supplied vector claims PR:N (unauthenticated), but the description does not confirm that catchimage is reachable without an authenticated/admin session - in many CMS deployments UEditor upload endpoints are gated behind login, which would materially reduce exposure; verify reachability in the specific deployment. Impact is confined to internal service probing/information inference, with no confirmed write or integrity effect. |
| Impact | Signals are mixed and lean toward lower real-world urgency than the 7.5 (HIGH) base score suggests. The provided CVSS vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated flaw, which on paper is attractive. However, EPSS is only 0.14% (3rd percentile), indicating a very low modeled probability of exploitation in the near term, and the vulnerability is NOT listed in CISA KEV - there is no evidence of active exploitation. The SSVC framework reports Exploitation: poc (proof-of-concept exists), Automatable: yes, and Technical Impact: partial; the 'partial' technical impact aligns better with a limited/blind SSRF than with the C:H (full confidentiality loss) encoded in the input vector. This is the key tension: the input vector claims C:H, but the description only describes probing internal HTTP services 'through response differences,' which is a semi-blind SSRF yielding limited data exposure - the C:H rating appears inflated, and 'partial' impact plus a loopback/link-local filter bypass is more consistent with C:L. Net assessment: a genuine SSRF worth patching, but given an obscure, low-footprint product, very low EPSS, no KEV listing, and only partial technical impact, this is a high-CVSS-but-moderate-real-risk issue rather than an emergency. Also note PR:N (unauthenticated) is asserted by the input vector but not corroborated by the description - UEditor upload endpoints are frequently gated behind authentication, so verify whether catchimage is reachable pre-auth in the affected deployment. |
| Exploit ScenarioDerived | An attacker sends a crafted request to the Feehi CMS UEditor catchimage endpoint supplying a URL pointing at a loopback (127.0.0.1) or link-local (169.254.0.0/16) address, which the private-IP validation fails to block. By observing differences in the server's responses, the attacker maps and probes internal-only HTTP services (admin panels, metadata endpoints, other internal hosts) that are not directly reachable from outside. A public proof-of-concept exists (SSVC Exploitation: poc), and the low attack complexity makes the technique straightforward to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Server-side request forgery in Feehi CMS 2.1.1 allows remote attackers to coerce the server into issuing HTTP requests to attacker-chosen URLs via the bundled UEditor 'catchimage' image-fetch endpoint, because the private-IP validation routine fails to block loopback (e.g. 127.0.0.1) and link-local (e.g. 169.254.169.254) destinations. The SSRF is semi-blind - the attacker infers internal service state through observable response differences rather than receiving full response bodies - so practical impact is limited to internal service probing and information disclosure, with no confirmed integrity or write effect; the supplied vector rates it 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), while the independent assessment downgrades confidentiality to Low (C:L) and notes that PR:N is unverified because catchimage may sit behind an authenticated CMS session. Publicly available exploit code exists (SSVC Exploitation: poc) and the issue is automatable, but there is no confirmed active exploitation (not in CISA KEV), and the EPSS score is low at 0.14% (3rd percentile), indicating limited near-term exploitation likelihood at scale.
RemediationAI
No vendor-released patch was identified at time of analysis, and the available references (the project repository https://github.com/liufee/cms and https://nvd.nist.gov/vuln/detail/CVE-2026-95265) do not point to a fixed Feehi CMS or UEditor release, so remediation must be compensatory. First, restrict reachability of the UEditor catchimage action: disable or remove the catchimage handler in the bundled UEditor deployment or block requests to its route at the reverse proxy/WAF - the trade-off is loss of remote-image localization for editor content, which only affects authors pasting external image URLs. Second, enforce authentication and admin-only access on all UEditor endpoints, since the description does not confirm that catchimage is reachable unauthenticated and the independent assessment flags that gating is likely in many CMS deployments; verify reachability in your specific instance before assuming exploitability. Third, apply egress filtering on the web server so it cannot initiate outbound connections to loopback (127.0.0.0/8, ::1), link-local (169.254.0.0/16), and - where operationally feasible - RFC1918 ranges, and explicitly deny access to cloud metadata endpoints such as 169.254.169.254; the trade-off is that overly broad egress blocks can break legitimate image fetching, so scope the rules to internal ranges only. Fourth, on AWS and similar platforms, enforce IMDSv2 (token-required) and hop-limit restrictions to blunt metadata-service abuse even if SSRF succeeds. Finally, monitor web server logs for catchimage requests whose URL parameters reference localhost, 127.0.0.1, 169.254.169.254, or other internal hosts, and treat such patterns as active exploitation attempts.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a classic CWE-918 Server-Side Request Forgery rooted in insufficient input validation of the target host in Feehi CMS's bundled UEditor rich-text editor. UEditor's 'catchimage' action is designed to retrieve remote images referenced in editor content and re-host them locally, which requires the server itself to perform an outbound HTTP fetch on a URL supplied by the client; the code applies a private-IP denylist but omits loopback (127.0.0.0/8, ::1) and link-local (169.254.0.0/16, notably the 169.254.169.254 cloud instance-metadata address) ranges, allowing the attacker to steer the fetch at internal-only endpoints. Because the endpoint is semi-blind, the attacker does not receive raw internal response bodies and instead relies on differential responses (status codes, error timing, size/content-type of the fetched 'image') to enumerate and fingerprint internal services - a lower-fidelity but still useful probing primitive, especially against cloud metadata services. The CPE supplied in the intelligence feed is unresolved (cpe:2.3:a:n/a:n/a:*:*:*:*:*:*:*:*), meaning no authoritative product/version CPE mapping is available and detection must rely on the vendor repository (https://github.com/liufee/cms) and the version string 2.1.1 rather than automated CPE-based scanning.
Know when Feehi Cms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Network-reachable, low-complexity SSRF; C:L (not H) because it is a semi-blind probe inferring state via response differences, consistent with SSVC 'partial' impact; no integrity or availability effect.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
3DescriptionCVE.org
Feehi CMS 2.1.1 contains a Server-Side Request Forgery (SSRF) vulnerability in the UEditor catchimage endpoint. The private-IP validation does not block loopback or link-local addresses, allowing an attacker to make the server probe internal HTTP services through response differences.
Executive ViewAI
Feehi CMS 2.1.1 exposes organizations to server-side request forgery through its bundled UEditor catchimage feature, which can be abused to make the CMS server probe internal services and potentially disclose sensitive information. Publicly available exploit code exists, and while the CVSS vector indicates unauthenticated access (PR:N), the advisory notes authentication requirements are unverified because catchimage may sit behind an authenticated CMS session. Because no vendor-released patch is available, internet-facing or internally exposed Feehi CMS 2.1.1 instances require immediate mitigation and monitoring to limit internal reconnaissance and information disclosure.
No vendor-released patch identified at time of analysis; restrict or disable the UEditor catchimage endpoint, implement egress filtering to block loopback, link-local, and private IP destinations, enforce cloud metadata endpoint protections (e.g., IMDSv2), and monitor for SSRF probing against internal services.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Feehi CMS 2.1.1 is affected by a Server-side request forgery (SSRF) vulnerability. Rated critical severity (CVSS 9.1), t
An arbitrary file upload vulnerability in the Advertising Management module of Feehi CMS v2.1.1 allows attackers to exec
A Host Header Injection vulnerability in Feehi CMS 2.1.1 may allow an attacker to spoof a particular header. Rated mediu
A stored cross-site scripting (XSS) vulnerability in /index.php?r=site%2Fsignup of Feehi CMS v2.1.1 allows attackers to
Incorrect access control in Feehi CMS 2.1.1 allows a low-privilege backend administrator who holds the administrator-upd
Arbitrary file deletion in Feehi CMS 2.1.1 allows an authenticated backend user holding article-edit permission to remov
Stored cross-site scripting (XSS) in Feehi CMS v2.1.1 Category module allows authenticated attackers to inject arbitrary
Stored cross-site scripting (XSS) in Feehi CMS v2.1.1 Permissions module allows authenticated users to inject malicious
EUVD-2026-92781
GHSA-hggc-x5gr-37ph
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB