CVE-2023-3800
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 was found in EasyAdmin8 2.0.2.2. It has been classified as problematic. Affected is an unknown function of the file /admin/index/index.html#/admin/mall.goods/index.html of the component File Upload Module. The manipulation leads to unrestricted upload. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-235068. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceUnrestricted file upload vulnerability in EasyAdmin8 2.0.2.2 File Upload Module at /admin/index/index.html#/admin/mall.goods/index.html allows attackers to upload arbitrary files without proper validation, potentially leading to remote code execution or serving malicious content.
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= 2.0.2.2CVSS 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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:H/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.
-
Confirm Easyadmin8 versionLocate the version file or admin panel footer that displays the installed Easyadmin8 version number. Common locations include a version.php file, admin dashboard footer, or system information page.Affected if The installed version is exactly 2.0.2.2 (no other versions are affected by this CVE)
-
Verify File Upload Module existsCheck if the admin interface includes the File Upload Module accessible at /admin/index/index.html#/admin/mall.goods/index.html by attempting to access this URL path in a browser or via curl.Affected if The path /admin/index/index.html#/admin/mall.goods/index.html is accessible and returns the File Upload Module interface
-
Confirm upload endpoint respondsSend a POST request to the upload endpoint used by the File Upload Module. This is typically the same URL or a related API endpoint under the mall.goods functionality.Affected if The upload endpoint accepts POST requests without returning validation errors or rejecting the request
-
Check for upload validationAttempt to upload a non-image file (such as a .php, .exe, or .js file) through the File Upload Module and observe if it is accepted or rejected.Affected if The system accepts file uploads without proper validation, allowing potentially malicious file types
You are affected if you have Wolfcode Easyadmin8 version 2.0.2.2 installed AND the File Upload Module at the specified admin path is accessible and accepts files without proper validation.
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 dataImplement server-side file type validation using magic byte inspection, enforce strict allowlists, store uploads outside webroot, rename uploaded files, and apply size limits to prevent executable file uploads.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3800 — 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-3800 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