VulnerabilityPublished 11 Jan 2024Updated 3 Jun 2025

CVE-2024-0414: DeShang DSCMS · Improper Access Controls

Affects DeShang DSCMSSource 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: 0.8% chance of exploitation in 30 days – higher than 56% 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 DSCMS	Affected 3.1.0 – 7.1 5 affected builds	Fixed in–

AI-suggested

Immediate assessment of all DeShang DSCMS instances to identify affected versions (3.1.0 through 3.1.2 and 7.0 through 7.1).
Restrict access to the public/install.php file at the web server or application firewall level, allowing only trusted IP addresses or internal networks to access it.
Implement strict web application firewall (WAF) rules to detect and block suspicious requests targeting installation or configuration endpoints.
Monitor web server logs for unusual access patterns or repeated attempts to access install.php or related resources.
If possible, disable or remove the installation script from production environments after initial setup to eliminate the attack vector.
Engage with the vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available.
Conduct regular vulnerability scans and penetration tests focusing on access control weaknesses in web applications.
Educate system administrators and security teams about this vulnerability and the importance of securing installation scripts and sensitive endpoints.
Consider network segmentation to isolate web-facing servers running DSCMS from critical internal systems to limit potential lateral movement.

Description

A vulnerability classified as problematic has been found in DeShang DSCMS up to 3.1.2/7.1. Affected is an unknown function of the file public/install.php. The manipulation leads to improper access controls. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-250434 is the identifier assigned to this vulnerability.

Impact

For European organizations using DeShang DSCMS, this vulnerability poses a risk of unauthorized access to installation or configuration components, potentially exposing sensitive data or system details. While the direct impact on integrity and availability is low, confidentiality breaches could lead to information leakage, which may include configuration secrets or user data. This could facilitate further targeted attacks such as privilege escalation or lateral movement within the network. Organizations in sectors with strict data protection regulations, such as finance, healthcare, and government, could face compliance risks and reputational damage if sensitive information is exposed. The remote and unauthenticated nature of the exploit increases the attack surface, especially for publicly accessible web servers running vulnerable DSCMS versions. The absence of known exploits in the wild currently reduces immediate risk, but the public disclosure means attackers could develop exploits rapidly. European organizations relying on DSCMS for web content management should prioritize assessment and mitigation to prevent potential breaches.

Summary

CVE-2024-0414 is a medium-severity vulnerability identified in DeShang DSCMS versions up to 3.1.2 and 7.1. The vulnerability stems from improper access controls (CWE-284) in an unspecified function within the public/install.php file of the DSCMS product. This flaw allows an unauthenticated attacker to remotely exploit the system without requiring user interaction. The vulnerability has a CVSS 3.1 base score of 5.3, indicating a moderate risk primarily impacting confidentiality with no direct impact on integrity or availability. The attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:N), and no user interaction needed (UI:N). The scope remains unchanged (S:U), meaning the vulnerability affects only the vulnerable component. The improper access control could allow an attacker to access sensitive installation or configuration routines that should be restricted, potentially exposing sensitive information or enabling further exploitation. Although no public exploits are currently known in the wild, the vulnerability details have been publicly disclosed, increasing the risk of exploitation. The lack of patches or mitigations provided by the vendor at this time further elevates the urgency for organizations to implement compensating controls. Given the vulnerability resides in a CMS system, which often hosts web content and manages user data, exploitation could lead to unauthorized data disclosure or facilitate subsequent attacks on the affected infrastructure.

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:25 UTC

WeaknessesCWE-284

Technical details

References

Community reviews

Related threats