Circutor SGE-PLC1000/SGE-PLC50 9.0.2 AddEvent stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Circutor SGE-PLC1000 and SGE-PLC50 9.0.2. This issue affects the function AddEvent. Performing a manipulation results in stack-based overflow. This vulnerability only affects products that are no longer supported by the maintainer.
This vulnerability is identified as CVE-2025-11783. The attack can only be performed from the local network. There is not any exploit available.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in Circutor SGE-PLC1000 and SGE-PLC50 9.0.2. It has been classified as critical. This affects the function AddEvent. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Stack-based buffer overflow vulnerability in Circutor SGE-PLC1000/SGE-PLC50 v9.0.2. The vulnerability is found in the 'AddEvent()' function when copying the user-controlled username input to a fixed-size buffer (48 bytes) without boundary checking. This can lead to memory corruption, resulting in possible remote code execution.
The weakness was released by Gabriel Gonzalez and Sergio Ruiz. The advisory is shared at incibe.es. This vulnerability is uniquely identified as CVE-2025-11783 since 10/15/2025. The exploitability is told to be easy. The attack can only be done within the local network. Technical details are known, but no exploit is available.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-200233). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Support
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 8.9VulDB Meta Temp Score: 8.7
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
10/15/2025 CVE reserved12/02/2025 Advisory disclosed
12/02/2025 VulDB entry created
12/04/2025 VulDB entry last update
Sources
Advisory: incibe.esResearcher: Gabriel Gonzalez, Sergio Ruiz
Status: Confirmed
CVE: CVE-2025-11783 (🔒)
GCVE (CVE): GCVE-0-2025-11783
GCVE (VulDB): GCVE-100-334041
EUVD: 🔒
Entry
Created: 12/02/2025 14:42Updated: 12/04/2025 10:06
Changes: 12/02/2025 14:42 (68), 12/02/2025 15:38 (1), 12/04/2025 10:06 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.