dbcve.org
Dso2oApplication · Csdeshang

CVE-2024-0358

HIGH · 7.5 CVSS v3.1 Published 2024-01-10
Fix available
A fix is available. Upgrade to after 4.1.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

The DeShang DSO2O e-commerce platform up to version 4.1.0 contains an improper access control vulnerability in the /install/install.php file. This allows remote attackers to access the installation script after the application has already been deployed, potentially allowing complete application reinstallation or configuration changes.

MitigationRemove the entire /install directory after successful installation, or implement proper access controls (e.g., IP whitelisting, authentication) on the install.php file to prevent unauthorized access.

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
Dso2oApplication
Affected:<= 4.1.0

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify if /install/install.php is accessible
    Attempt to access the URL path /install/install.php on the web server using a browser or HTTP client (e.g., curl http://target.example.com/install/install.php). Check if the page loads or returns an HTTP 200 response rather than a 404 or 403 error.
    Affected if The install.php script is accessible and returns a valid response (not 404/403), indicating the installation directory was not removed or protected after initial deployment.
  2. Check for presence of the /install directory
    On the server filesystem, examine whether the /install directory still exists in the web application's root directory (commonly named /www, /htdocs, /public_html, or the application's base folder).
    Affected if The /install directory exists on the server, which is required for the vulnerability to be exploitable.
  3. Determine the installed DSO2O version
    Locate the version identifier in the application's source code - typically found in a version file, configuration file, or the footer/admin panel of the application. Common paths include /data/config.php, /application/config.php, or a dedicated version file.
    Affected if The installed version is 4.1.0 or lower, matching the vulnerable version range.
  4. Verify if install.php shows reinstallation prompts
    If /install/install.php is accessible, examine whether it displays installation steps, a welcome screen, or database configuration fields rather than indicating the system is already installed.
    Affected if The script displays installation or configuration prompts, confirming the improper access control allows the full installation workflow to be accessed.

A user is affected if the DSO2O version is 4.1.0 or lower AND the /install/install.php script remains accessible on the web server without proper access restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 4.1.0
Interim mitigation

Remove the entire /install directory after successful installation, or implement proper access controls (e.g., IP whitelisting, authentication) on the install.php file to prevent unauthorized access.

Fix this in Dso2o Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0358 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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