1Panel-dev CordysCRM up to 1.4.1 Third Party Endpoint TokenService.java mkAddress server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 1.11 |
Summary
A vulnerability classified as critical was found in 1Panel-dev CordysCRM up to 1.4.1. Impacted is an unknown function of the file backend/crm/src/main/java/cn/cordys/crm/integration/sso/service/TokenService.java of the component Third Party Endpoint. Executing a manipulation of the argument mkAddress can lead to server-side request forgery. The identification of this vulnerability is CVE-2026-16222. The attack may be launched remotely. Furthermore, there is an exploit available. The project closed the issue report, stating that this is not the official way to report a security vulnerability.
Details
A vulnerability classified as critical was found in 1Panel-dev CordysCRM up to 1.4.1. This vulnerability affects an unknown function of the file backend/crm/src/main/java/cn/cordys/crm/integration/sso/service/TokenService.java of the component Third Party Endpoint. The manipulation of the argument mkAddress with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-16222. The exploitation appears to be easy. The attack can be initiated remotely. Technical details and also a public exploit are known.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The project closed the issue report, stating that this is not the official way to report a security vulnerability.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
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: 🔒
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
07/18/2026 Advisory disclosed07/18/2026 VulDB entry created
07/18/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 2685/2686
Status: Not defined
CVE: CVE-2026-16222 (🔒)
GCVE (CVE): GCVE-0-2026-16222
GCVE (VulDB): GCVE-100-380044
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/18/2026 14:16Changes: 07/18/2026 14:16 (58)
Complete: 🔍
Submitter: liushaozhe
Cache ID: 216::103
Submit
Accepted
- Submit #858043: 1Panel-dev CordysCRM 1.4.1 Server-Side Request Forgery (by liushaozhe)
Duplicate
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.