SVID:202607170001Pending assignmentSummary
The SCP (Supplier Collaboration Platform) exposed a supplier information query endpoint that required no authentication. An anonymous attacker could call it directly to retrieve 663 complete supplier records in bulk, including sensitive personal and corporate data: company names, legal representative names, unified social credit codes, registered capital, personnel scale, registered addresses, product categories and internal user IDs.
The issue was discovered by the Sigenergy Cybersecurity Red Team during routine offensive-security testing and has since been remediated. A second, lower-severity finding (password-reset user enumeration) is noted in the References section.
Handling Timeline
Vulnerability reported
The unauthenticated access was reported to the Sigenergy Security Incident Response Team by the Sigenergy Cybersecurity Red Team.
Fix deployed
Authentication enforcement was added to the affected endpoint.
Fix verified
Retesting confirmed unauthenticated requests are now rejected.
Affected Products / Components
| Endpoint | Environment |
|---|---|
| /srm/admin/app/sgSupplierBasicInfo/queryReviewSupplierList | Production (scp.sigenergy.com) |
| /srm/admin/upms/passwordReset/prepare | Production (scp.sigenergy.com) |
Vulnerability Description
The supplier query endpoint performs no authentication or authorization check. Any anonymous request returns the full list of supplier records, disclosing:
- Company information — company name (Chinese and English), unified social credit code, registered capital, personnel scale, registered address.
- Personal information — legal representative name.
- Internal identifiers — supplier code, internal user ID, update user ID, product classification and agent brands.
Proof of Concept
Before the fix — an unauthenticated request returned complete supplier records (values redacted):
2026-02-05T10:49:00.000+00:00 1923********** 2026-07-17T23:45:51.000+00:00 MS01****93 苏州**科技有限公司 00001 91320505MAC****** 2022-11-10T16:00:00.000+00:00 袁* 15 300 C 昆山开发区丰源汇杰雅苑*号楼*室
After the fix — the same request without a token is rejected:
{"errorCode":"UNAUTHORIZED_LOGIN","errorMessage":"非免登录接口必须包含Token信息!","success":false,"traceId":"6a1a6c86d7c24e888035b3c0b41c0559"}
Root Cause
- Missing authentication. The endpoint does not verify that the request carries a valid login token.
- Missing authorization. No check is performed to confirm the caller is entitled to read supplier records.
CVSS v4.0 Scoring
The report assigns a CVSS v4.0 Base Score of 8.7 (High).
| Metric | Value | Meaning |
|---|---|---|
| Attack Vector (AV) | Network | Exploitable over the internet. |
| Attack Complexity (AC) | Low | No special conditions required. |
| Attack Requirements (AT) | None | No preconditions. |
| Privileges Required (PR) | None | No authentication required. |
| User Interaction (UI) | None | No victim interaction. |
| Vulnerable System Confidentiality (VC) | High | Discloses 663 supplier records with PII. |
| Vulnerable System Integrity (VI) | None | No data modification. |
| Vulnerable System Availability (VA) | None | No availability impact. |
| Subsequent System Confidentiality (SC) | None | No impact beyond the component. |
| Subsequent System Integrity (SI) | None | No impact beyond the component. |
| Subsequent System Availability (SA) | None | No impact beyond the component. |
Impact
A successful attack exposes the sensitive corporate and personal data of Sigenergy suppliers:
- Supplier data disclosure — 663 complete supplier records including names, legal representatives, credit codes and addresses.
- Enables further attacks — the exposed data can be used for targeted phishing, business fraud and social engineering.
Remediation & Recommendations
- Enforce authentication on the supplier query endpoint — unauthenticated requests now receive
UNAUTHORIZED_LOGIN. - Apply authentication and authorization consistently across all
/srm/admin/**endpoints. - Minimize sensitive fields returned by supplier endpoints (credit codes, legal representative names, addresses).
- Uniform error messages for login / password-reset flows to prevent account enumeration.
Additional hardening (recommended)
- Add rate limiting and anomaly detection to flag bulk enumeration.
- Log and alert on anonymous access attempts to administrative endpoints.
- Run periodic broken-authentication / broken-object-level-authorization testing across the API surface.
References
- Weakness:
CWE-306(Missing Authentication for Critical Function) /CWE-200(Exposure of Sensitive Information) - OWASP API Security Top 10 2023 —
API1:2023(Broken Object Level Authorization) andAPI2:2023(Broken Authentication)
POST /srm/admin/upms/passwordReset/prepare — differing error codes (NO-ERROR vs PASSWORD_RESET_INVALID_ACCOUNT) allow account enumeration and partial email disclosure (e.g. k*****@sigenergy.com). See CWE-204 (Observable Response Discrepancy).