CVE-2023-34207
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 · uneditedUnrestricted upload of file with dangerous type vulnerability in create template function in EasyUse MailHunter Ultimate 2023 and earlier allows remote authenticated users to perform arbitrary system commands with ‘NT Authority\SYSTEM‘ privilege via a crafted ZIP archive.
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 EasyUse MailHunter Ultimate 2023's create template function allows authenticated remote attackers to upload malicious files via crafted ZIP archives. The application fails to properly validate file types and contents within uploaded archives, enabling attackers to upload and execute arbitrary code with NT Authority\SYSTEM privileges.
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<= 2023CVSS 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 EasyUse MailHunter Ultimate installationSearch for MailHunter installation directories (commonly in C:\Program Files\ or C:\Program Files (x86)\) or check Windows Programs and Features for 'EasyUse MailHunter Ultimate' entryAffected if The software is installed on the system
-
Determine installed versionRight-click the application executable or DLL, select Properties, then view Version tab; alternatively check the About section within the application's web interface if accessibleAffected if Version displays as 2023 or any year prior (e.g., 2022, 2021, etc.) indicating a version <= 2023
-
Verify web interface accessibilityOpen a browser and attempt to access the application's web portal (default ports are often 80, 443, or 8080; check documentation for the specific port configuration)Affected if The web interface is reachable over the network
-
Confirm create template function existsLog into the web interface and navigate to the template creation area (typically under Settings, Templates, or Create New sections); look for a ZIP archive upload option within this featureAffected if The create template functionality with ZIP upload capability is present and accessible
-
Inspect upload directories for unexpected filesExamine the application's designated upload folders (commonly found in the webroot, App_Data, or a dedicated uploads folder within the installation directory) for files with executable extensions such as .asp, .aspx, .php, .exe, or .dll that were not intentionally placed thereAffected if Unexpected executable files are found in upload directories, particularly outside of expected subfolders or with disguised extensions
The environment is likely affected if EasyUse MailHunter Ultimate version 2023 or earlier is installed and its web-based create template function with ZIP upload is accessible, regardless of authentication status.
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 strict allowlist-based file type validation for uploaded ZIP archives and their contents, sanitize filenames and extensions, store uploads outside webroot with non-executable permissions, and process uploads with least-privilege service accounts rather than SYSTEM.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34207 — 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-34207 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