CVE-2024-0358: DeShang DSO2O · Improper Access Controls
Affects DeShang DSO2OSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| DeShang DSO2O | Affected
| Fixed in– |
AI-suggested
1. Immediate mitigation should include restricting external access to the /install/install.php script through network controls such as firewalls or web application firewalls (WAFs), limiting exposure to trusted internal networks only. 2. Organizations should audit their DSO2O installations to confirm the version in use and identify if the vulnerable versions 4.0 or 4.1 are deployed. 3. Until an official patch is released, consider disabling or removing the installation script if it is not required for ongoing operations. 4. Implement strict access control policies around installation and configuration files, ensuring only authorized personnel can access these resources. 5. Monitor logs and network traffic for unusual access attempts to the installation script or related endpoints. 6. Engage with the vendor for timely updates and apply patches as soon as they become available. 7. Conduct a security review of the application’s deployment architecture to ensure proper segmentation and minimize exposure of critical components. 8. Educate IT and security teams about this vulnerability to raise awareness and readiness to respond to any exploitation attempts.
Description
A vulnerability was found in DeShang DSO2O up to 4.1.0. It has been classified as critical. This affects an unknown part of the file /install/install.php. The manipulation leads to improper access controls. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-250125 was assigned to this vulnerability.