CVE-2023-34208
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 · uneditedPath Traversal in create template function in EasyUse MailHunter Ultimate 2023 and earlier allow remote authenticated users to extract files into arbitrary directories 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 confidenceA path traversal vulnerability in the create template function of EasyUse MailHunter Ultimate 2023 and earlier allows authenticated remote users to upload crafted ZIP archives containing files with path traversal sequences (e.g., ../../filename), enabling arbitrary file extraction to directories outside the intended template directory.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm EasyUse MailHunter Ultimate installationLocate the EasyUse MailHunter Ultimate application on the system or identify it via installed programs list. Note the exact version number displayed.Affected if The application is installed and version displays as 2023 or earlier (e.g., 2022, 2021, etc.)
-
Identify template creation feature accessDetermine whether authenticated user accounts exist that have access to the template creation or import functionality within the application.Affected if Authenticated users can access the template creation/import feature
-
Verify ZIP archive upload capabilityCheck if the template import feature accepts ZIP file uploads - this is the attack vector for the path traversal vulnerability.Affected if The template creation function accepts ZIP archive uploads from users
-
Review for path traversal protectionInspect application logs or template extraction behavior to determine if path traversal sequences (..) within ZIP archives are validated or blocked before extraction.Affected if No validation of path traversal sequences is performed on ZIP contents before extraction, allowing files to be placed outside the intended template directory
-
Check authentication requirementsVerify whether the template upload feature requires authentication, as the CVE requires authenticated remote users.Affected if The template creation/upload feature is accessible to authenticated users without additional security controls on path traversal
The environment is affected if EasyUse MailHunter Ultimate version 2023 or earlier is installed, the template creation feature accepts ZIP uploads, and path traversal sequences within ZIP archives are not validated before extraction.
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 validation of file paths within ZIP archives before extraction, including checking for and rejecting path traversal sequences (..), ensuring extracted files remain within the designated template directory, and using secure path resolution methods.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34208 — 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-34208 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