WuzhiCMS up to 4.1.0 Remote Image Fetch index.php ckditor::saveRemote source[] server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.89 |
Summary
A vulnerability, which was classified as critical, was found in WuzhiCMS up to 4.1.0. This affects the function ckditor::saveRemote of the file coreframe/app/attachment/index.php of the component Remote Image Fetch. Such manipulation of the argument source[] leads to server-side request forgery.
This vulnerability is uniquely identified as CVE-2026-92380. The attack can be launched remotely. Moreover, an exploit is present.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability was found in WuzhiCMS up to 4.1.0. It has been rated as critical. Affected by this issue is the function ckditor::saveRemote of the file coreframe/app/attachment/index.php of the component Remote Image Fetch. The manipulation of the argument source[] with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality, integrity, and availability.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-92380. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known.
The exploit is available at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet. By approaching the search of inurl:coreframe/app/attachment/index.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Google Hack: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/16/2026 Advisory disclosed09/16/2026 VulDB entry created
09/16/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 221
Status: Not defined
CVE: CVE-2026-92380 (🔒)
GCVE (CVE): GCVE-0-2026-92380
GCVE (VulDB): GCVE-100-405512
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/16/2026 09:48Changes: 09/16/2026 09:48 (59)
Complete: 🔍
Submitter: ZAST.AI
Cache ID: 216::103
Submit
Accepted
- Submit #935194: wuzhicms <=4.1.0 SSRF (by ZAST.AI)
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.