CVE-2021-38847
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 · uneditedS-Cart v6.4.1 and below was discovered to contain an arbitrary file upload vulnerability in the Editor module on the Admin panel. This vulnerability allows attackers to execute arbitrary code via a crafted IMG file.
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 · high confidenceS-Cart v6.4.1 and below contains an arbitrary file upload vulnerability in the Editor module accessible via the Admin panel. Attackers can upload a crafted image file containing malicious code (e.g., PHP web shell) and execute it to achieve remote code execution on the server.
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<= 6.4.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
- 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 installed S-Cart versionLocate the version file or admin dashboard footer that displays the current S-Cart version numberAffected if The installed version is 6.4.1 or lower
-
Verify Editor module statusAccess the Admin panel and check if the Editor module is installed and enabled in the module management sectionAffected if The Editor module is active and accessible
-
Confirm Admin panel accessibilityAttempt to access the Admin panel login page and determine if it is publicly reachable via the networkAffected if The Admin panel is exposed without proper access controls or authentication requirements
-
Inspect upload directory contentsExamine the directory configured for file uploads (typically in storage or public/uploads) for unexpected file extensions such as .php, .phtml, or double extensions like .php.jpgAffected if Script executable files are present in upload directories outside the webroot or with executable permissions
-
Review web server upload configurationCheck the web server configuration (Apache .htaccess, Nginx config) for the upload directories to verify if script execution is disabledAffected if Script execution is allowed in upload directories or no execution prevention is configured
You are affected if running S-Cart version 6.4.1 or lower with the Editor module enabled and the Admin panel accessible, particularly if upload directories permit script execution.
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 dataRestrict Admin panel access to authorized personnel only; implement strict file type validation using magic byte checks rather than extension alone; store uploaded files outside the webroot or disable script execution in upload directories; update to a patched version if available.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-38847 — 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-2021-38847 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