CVE-2024-0414
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA critical access control vulnerability exists in DeShang DSCMS public/install.php, allowing unauthenticated remote attackers to access the installation script after initial setup. Since the installer is publicly accessible without proper authorization checks, attackers can potentially re-run the installation process to modify configurations, reset the database, or execute arbitrary code depending on the installer's functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.1.0, <= 3.1.2= 7.0= 7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the DSCMS installationLocate the web application root directory and check for DSCMS-specific files such as include/config.php, include/common.php, or admin/login.php to confirm the product is Csdeshang DscmsAffected if The application is confirmed to be Csdeshang Dscms
-
Check the DSCMS versionOpen include/common.php or a version information file within the DSCMS installation and locate the version number defined in the codeAffected if The installed version is >= 3.1.0 and <= 3.1.2, or equals 7.0 or 7.1
-
Verify public/install.php existsCheck the presence of the file public/install.php in the web root directory of the DSCMS installationAffected if The file public/install.php exists on the server
-
Test installer accessibilityAttempt to access the URL path /public/install.php via HTTP request from an unauthenticated context (e.g., using curl or a browser without logging in)Affected if The installer script returns a response and is accessible without authentication
-
Confirm installer is still functionalCheck if the installer presents an active installation form or wizard interface rather than a disabled/locked state messageAffected if The installer returns an active installation interface or does not redirect to a disabled state
A user is affected if their environment runs Csdeshang Dscms version 3.1.0-3.1.2, 7.0, or 7.1 AND the public/install.php file exists and remains accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately restrict or remove public/install.php to prevent unauthorized access; implement proper authentication and authorization checks if the installer must remain functional, and ensure the installer is disabled or deleted after initial installation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0414 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0414 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data