VulnerabilityPublished 11 Jan 2024Updated 3 Jun 2025

CVE-2024-0411: DeShang DSMall · Improper Access Controls

Affects DeShang DSMallSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.2% chance of exploitation in 30 days – higher than 82% 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:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
DeShang DSMall	Affected =6.0 =6.1	Fixed in–

AI-suggested

Immediate mitigation should include restricting access to the public/install.php file via web server configuration (e.g., using .htaccess rules or equivalent) to allow only trusted IP addresses or internal networks to access it.
Disable or remove the install.php script entirely after installation is complete to eliminate the attack surface.
Implement web application firewall (WAF) rules to detect and block suspicious HTTP GET requests targeting install.php or unusual parameter manipulations.
Monitor web server logs for anomalous access patterns to install.php and related endpoints to detect potential exploitation attempts.
Engage with DeShang vendor support or security advisories to obtain patches or updates as soon as they become available and plan for timely application.
Conduct a security review of access control mechanisms across the DSMall deployment to identify and remediate any other potential weaknesses.
Educate system administrators and developers on secure deployment practices, emphasizing the importance of removing or securing installation scripts post-deployment.

Description

A vulnerability was found in DeShang DSMall up to 6.1.0. It has been classified as problematic. This affects an unknown part of the file public/install.php of the component HTTP GET Request Handler. 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 associated identifier of this vulnerability is VDB-250431.

Impact

For European organizations using DeShang DSMall versions 6.0 or 6.1, this vulnerability poses a risk of unauthorized information disclosure due to improper access controls. While the impact is limited to confidentiality and does not affect data integrity or service availability, sensitive installation or configuration data could be exposed, which might facilitate further attacks or unauthorized system reconnaissance. Organizations in sectors such as e-commerce, retail, or any business relying on DSMall for online storefronts could face reputational damage and compliance issues under GDPR if sensitive customer or operational data is leaked. The remote and unauthenticated nature of the exploit increases the threat level, especially for publicly accessible DSMall installations. Given the lack of a patch, organizations must prioritize mitigating this vulnerability to prevent potential exploitation that could lead to broader security incidents.

Summary

CVE-2024-0411 is a medium-severity vulnerability identified in DeShang DSMall versions 6.0 and 6.1. The vulnerability stems from improper access controls (CWE-284) in the HTTP GET request handler, specifically within the public/install.php file. This flaw allows an unauthenticated remote attacker to manipulate access controls, potentially bypassing restrictions that should prevent unauthorized actions. The vulnerability does not require any user interaction or privileges to exploit, and the attack surface is exposed via network (AV:N), making it remotely exploitable with low attack complexity (AC:L). The impact is limited to confidentiality, with no direct effect on integrity or availability. Although no known exploits are currently observed in the wild, the public disclosure of the vulnerability increases the risk of exploitation. The lack of a patch link suggests that remediation may not yet be available, emphasizing the need for immediate mitigation measures. The vulnerability's presence in the installation script (install.php) indicates that attackers might leverage it to gain unauthorized access or gather sensitive information during or after the installation process, potentially compromising the deployment environment or configuration data.

CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Embedding Scripts within Scripts (opens in a new tab)
Modification of Windows Service Configuration (opens in a new tab)
Malicious Root Certificate (opens in a new tab)
Intent Spoof (opens in a new tab)
WebView Exposure (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Jul 2025, 15:26 UTC

WeaknessesCWE-284

Technical details

References

Community reviews

Related threats