Security Advisory

Security Advisories

Vulnerability disclosures and security advisories published by Sigenergy CSIRT, with CVSS 4.0 severity ratings and remediation guidance.

9.3/10 Critical
SVID:202412060001 · CVSS v4.0

Unauthorized MQTT Broker Access (Port 1883/8883)

The SigenCloud MQTT broker accepts anonymous connections on ports 1883 and 8883, allowing unauthenticated subscribe and publish of device telemetry and control messages.

Affected: SigenCloud MQTT Broker — Port 1883 / 8883 Reported: 2024-12-06 Status: Fixed
9.2/10 Critical
SVID:202409120001 · CVSS v4.0

Spring Boot Actuator Heap Dump Information Disclosure

An unauthenticated Spring Boot Actuator /actuator/heapdump endpoint on api.sigencloud.com exposed a full JVM heap dump that may contain credentials, session tokens and cached personal data.

Affected: SigenCloud API — Spring Boot Actuator Detected: 2024-09-12 Status: Fixed
7.1/10 High
SVID:202409200001 · CVSS v4.0

Unauthorized Swagger UI Access and API Information Disclosure

Unauthenticated Swagger UI and API documentation endpoints on api-eu.sigenergy.com expose the full API surface, request parameters and sensitive business fields.

Affected: SigenCloud API — Swagger UI / API Docs Reported: 2024-09-20 Status: Fixed
8.2/10 High
SVID:202403220001 · CVSS v4.0

Insecure Direct Object Reference in Device Signal Write API

Missing object-level authorization lets any authenticated user write arbitrary signal values to another customer's inverter by changing the deviceSnCode and stationId.

Affected: SigenCloud Device Signal Write API Reported: 2024-03-22 Status: Fixed
8.7/10 High
SVID:202403280001 · CVSS v4.0

Arbitrary User Password Reset in SigenCloud

Account enumeration, a brute-forceable CAPTCHA, and a weak 4-digit password-reset verification code allow an attacker to reset any user's password and take full control of the account.

Affected: SigenCloud Portal & Admin API Published: 2024-03-29 Status: Fixed
5.3/10 Medium
SVID:202511090001 · CVSS v4.0

HTML Injection in Device-Sharing Invitation Email

Unsanitized firstName/lastName fields in the device-sharing invitation API allow HTML injection into the invitation email, enabling phishing and content spoofing.

Affected: SigenCloud Device Sharing Email Notification Published: December 2025 Status: Fixed
7.1/10 High
SVID:202511090002 · CVSS v4.0

Insecure Direct Object Reference in Station Home API

Missing object-level authorization lets an authenticated user read other customers' station data — name, home address, GPS coordinates and serial numbers — by changing the stationId parameter.

Affected: SigenCloud Device Owner Station API Published: 2025-11-09 Status: Fixed
7.1/10 High
SVID:202609150001 · CVSS v4.0

Missing Authorization Checks — Data Disclosure

Missing authorization across multiple SigenCloud endpoints lets an installer account read other users' personal data, plants and devices.

Affected: SigenCloud — Multiple API Endpoints Reported: 2026-09-15 Status: Fixed
6.9/10 High
SVID:202609150002 · CVSS v4.0

Missing Authorization Checks — Email Sending as Sigenergy

Missing authorization on the email-send endpoint lets an installer account send emails as Sigenergy, enabling phishing campaigns.

Affected: SigenCloud — Email Send Endpoint Reported: 2026-09-15 Status: Fixed
8.7/10 High
SVID:202608200001 · CVSS v4.0

Unauthenticated Supplier Information Enumeration in SCP

The searchSupplierByKeyword endpoint required no authentication, allowing anonymous enumeration of 515 suppliers — including 14 core material suppliers that reveal the supply-chain structure.

Affected: SCP — searchSupplierByKeyword Reported: 2026-08-20 Status: Fixed
8.7/10 High
SVID:202607170001 · CVSS v4.0

SCP Supplier Data Unauthorized Access

The sgSupplierBasicInfo/queryReviewSupplierList endpoint required no authentication, exposing 663 complete supplier records including company names, legal representatives, unified social credit codes and registered addresses.

Affected: SCP — sgSupplierBasicInfo/queryReviewSupplierList Reported: 2026-07-17 Status: Fixed

Reporting a Vulnerability

We encourage security researchers, customers, and partners to report suspected vulnerabilities in Sigenergy products. Reports are handled in line with ISO/IEC 29147 and ISO/IEC 30111.

When reporting, please include detailed exploitation steps and supporting evidence such as a proof of concept (PoC). See CVE ID Assignment for how CVE IDs are assigned and published.