CVE-2023-1185
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, which was classified as problematic, was found in ECshop up to 4.1.8. This affects an unknown part of the component New Product Handler. The manipulation leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-222357 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 confidenceECshop up to version 4.1.8 contains an unrestricted file upload vulnerability in the New Product Handler component, allowing remote authenticated or unauthenticated attackers to upload arbitrary files (likely webshells) leading to remote code execution. The exploit is publicly available.
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<= 4.1.8CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 ECshop installation and versionCheck your web server for ECshop installation directories (commonly /ecshop, /shop, or similar paths). Look for a version file or check the footer/admin panel for the installed version number. Compare your version to the affected range: versions 4.1.8 and below are vulnerable.Affected if Your installed ECshop version is 4.1.8 or lower, or you cannot determine the version and ECshop is present
-
Locate the New Product Handler componentSearch for files related to 'new product', 'product handler', or 'goods' functionality in the ECshop installation, typically in /admin or /includes directories. The vulnerable component handles product-related operations and accepts file uploads.Affected if The New Product Handler component exists and is accessible in your ECshop installation
-
Verify upload functionality is exposedCheck if the product upload functionality is accessible without authentication or from the admin panel. Test accessing the product creation/modification endpoint. Look for file upload forms that accept file attachments for products.Affected if The file upload functionality in the product handler is accessible without proper restrictions
-
Inspect upload directories for suspicious filesExamine directories where ECshop stores uploaded files (commonly /images, /uploads, or /temp). Look for file types that should not be present such as .php, .phtml, .asp, .jsp, or .exe files. Check file creation dates and origins.Affected if Unexpected script files (.php, .phtml, etc.) exist in upload directories, especially if they were not intentionally uploaded by administrators
You are affected if ECshop version 4.1.8 or lower is installed and the New Product Handler upload functionality is accessible, or if suspicious script files exist in upload directories.
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 dataUpgrade to a patched version of ECshop beyond 4.1.8, or implement strict file type/extension validation, rename uploaded files, and disable script execution in upload directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1185 — 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-2023-1185 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