MeterSphere EUVD-2026-98472

Requires an authenticated low-privilege account on the MeterSphere instance (PR:L) and access to the Swagger3 API-definition import feature; the attacker must be able to control the swaggerUrl argument passed to Swagger3ParserApiDefinition.testUrlTimeout. No user interaction is needed (UI:N) and the attack is network-reachable (AV:N) with low complexity (AC:L). Limiting factors: exploitation is gated by valid credentials and access to the API-import functionality, and real-world impact depends on the server's internal network reachability (e.g., presence of internal services, cloud metadata endpoints, or weak egress/segmentation controls); affects versions up to 3.6.9-lts.

This is a moderate, not high, priority. The CVSS 4.0 base score is 5.3 (Medium), and the vector CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L shows a network-reachable, low-complexity SSRF that nonetheless requires PR:L - i.e. an authenticated low-privilege account - which materially limits the attacker population to users who already have access to the MeterSphere instance. Exploitation status is 'publicly available exploit code exists' (the disclosure states the exploit is public and the E:P / Proof-of-Concept exploit maturity in the vector corroborates this), but there is no CISA KEV listing and no EPSS score was provided, so there is no evidence of active, widespread exploitation - POC availability is a distinct signal from in-the-wild use and must not be conflated. The impact metrics (VC:L/VI:L/VA:L, SC:N/SI:N/SA:N) indicate limited, non-cascading impact confined to the vulnerable system, consistent with a classic SSRF that can reach internal services or metadata endpoints but does not by itself grant full compromise. Notably, the vendor was contacted but did not respond, so there is no confirmed patched version - a defensive gap worth flagging. Net: a real but bounded risk, best treated as a standard-priority patch/mitigation item rather than an emergency, with elevated concern only in environments where the MeterSphere UI is broadly accessible or internal network segmentation is weak.

An authenticated low-privilege MeterSphere user invokes the Swagger3 API import feature and supplies a malicious URL in the swaggerUrl argument, causing the server to issue an attacker-controlled request to an internal host (e.g., a cloud metadata service or an internal admin panel). A public proof-of-concept exists, lowering the skill required; the attacker uses the server's trusted network position to probe or reach services otherwise unreachable from outside.