Is there a public PoC exploit available for CVE-2026-16223?

Yes, a public proof-of-concept exploit is available for CVE-2026-16223. Prioritise patching immediately. EPSS: 0.2%.

CordysCRM CVE-2026-16223

Q: What is the CVSS score of CVE-2026-16223?

CVE-2026-16223 has a CVSS 4.0 base score of 2.1 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-45433 LOW

Server-Side Request Forgery (SSRF) (CWE-918)

2026-07-19 VulDB

GHSA-3gm6-8rm6-q59f

Java SSRF Cordyscrm 1Panel Dev

2.1

CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY

2.1 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

5.0 MEDIUM

Network-exploitable with low-privilege auth; scope change applies as SSRF reaches systems beyond the vulnerable component; no direct integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Severity Changed

Jul 19, 2026 - 08:22 NVD

MEDIUM LOW

CVSS changed

Jul 19, 2026 - 08:22 NVD

5.3 (MEDIUM) 2.1 (LOW)

Analysis Generated

Jul 19, 2026 - 08:21 vuln.today

CVE Published

Jul 19, 2026 - 07:15 cve.org

MEDIUM 5.3

DescriptionCVE.org

A vulnerability was determined in 1Panel-dev CordysCRM up to 1.4.1. Impacted is the function getSqlBotSrc of the file backend/crm/src/main/java/cn/cordys/crm/system/service/IntegrationConfigService.java of the component Third Party Edit Endpoint. Executing a manipulation of the argument appSecret can lead to server-side request forgery. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized.

AnalysisAI

Server-side request forgery in CordysCRM (1Panel-dev) up to version 1.4.1 allows authenticated remote attackers to coerce the application server into issuing outbound HTTP requests to arbitrary destinations by manipulating the appSecret parameter in the Third Party Edit Endpoint's getSqlBotSrc function. This can expose internal network services, cloud instance metadata endpoints, and other non-public resources to an attacker with only a low-privileged account. A public exploit has been disclosed (GitHub issue #2688), meaning exploitation requires minimal technical skill beyond valid credentials.

Technical ContextAI

CordysCRM is a Java-based CRM platform maintained by 1Panel-dev. The vulnerability is located in backend/crm/src/main/java/cn/cordys/crm/system/service/IntegrationConfigService.java within the getSqlBotSrc method, which processes third-party integration configuration. CWE-918 (Server-Side Request Forgery) describes the root cause: the appSecret argument is consumed without sufficient URL validation or allowlist enforcement before the application constructs and dispatches an outbound HTTP request. This allows an attacker to redirect server-initiated requests to RFC 1918 private addresses, loopback interfaces, cloud metadata services (e.g., 169.254.169.254 on AWS/GCP/Azure), or other internal endpoints the server can reach but the attacker cannot directly. The CPE cpe:2.3:a:1panel-dev:cordyscrm:*:*:*:*:*:*:*:* covers all releases through 1.4.1.

RemediationAI

No vendor-released patch with a confirmed fixed version has been identified at time of analysis; the upstream fix status should be monitored via GitHub issue https://github.com/1Panel-dev/CordysCRM/issues/2687 and the project repository at https://github.com/1Panel-dev/CordysCRM/. As an immediate compensating control, restrict access to the Third Party Edit Endpoint to administrator-level roles only, reducing the attacker pool from all authenticated users to privileged operators - note this may interrupt legitimate low-privileged integration configuration workflows. Additionally, enforce an outbound HTTP allowlist at the network perimeter or application gateway to block server-initiated connections to RFC 1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), loopback (127.0.0.1), and cloud metadata addresses (169.254.169.254) - carefully scope exceptions to avoid breaking legitimate third-party integrations. For cloud deployments, enforcing IMDSv2 on all instances significantly reduces the credential-theft risk even if SSRF is triggered, as IMDSv2 requires a session-oriented PUT request that is not possible through naive SSRF.