CVE-2026-75340

JetLinks · JetLinks Community

JetLinks Community version 2.11 contains a server-side request forgery (SSRF) vulnerability in the device metadata import interface, allowing unauthenticated attackers to perform unauthorized requests.

Executive summary

A critical server-side request forgery vulnerability in JetLinks Community 2.11 exposes the internal network to unauthorized access by unauthenticated attackers.

Vulnerability

The application fails to properly validate user-supplied input within the device metadata import interface located at /device/instance/{productId}/property-metadata/import. This allows an unauthenticated attacker to force the server to make arbitrary HTTP requests to internal or external resources.

Business impact

Successful exploitation of this SSRF vulnerability poses a severe risk to the confidentiality and integrity of the internal network. With a CVSS score of 9.1, this flaw could allow attackers to bypass perimeter defenses, access sensitive internal services, or exfiltrate configuration data. Such unauthorized access can lead to significant data breaches and total loss of control over the affected infrastructure.

Remediation

Immediate Action: Since a specific patch version is not currently listed, administrators should restrict access to the affected management interface via network segmentation or firewall rules until an official security update is released.

Proactive Monitoring: Monitor server access logs for suspicious requests to the /device/instance/ path and egress traffic logs for unusual outbound connections originating from the application server.

Compensating Controls: Deploy a Web Application Firewall (WAF) to inspect and block requests containing malicious payloads targeting the metadata import endpoint.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists and is attributed to the researcher's technical write-up referenced in the CVE record.

Analyst recommendation

Given the critical nature of this SSRF vulnerability and the availability of a proof-of-concept, immediate defensive action is required. Organizations running JetLinks Community 2.11 must prioritize restricting network access to the vulnerable endpoint and monitor for any signs of exploitation while awaiting an official vendor patch.

Sources