CVE-2023-4593
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 vulnerability whose exploitation could allow an authenticated remote user to bypass SecurityManager's intended restrictions and list a parent directory via any filename, such as a multiple ..%2F value affecting the 'dodoc' parameter in the /MailAdmin_dll.htm 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 · moderate confidencePath traversal vulnerability in /MailAdmin_dll.htm where the 'dodoc' parameter accepts encoded directory traversal sequences (multiple ..%2F values), allowing authenticated remote users to bypass SecurityManager restrictions and access parent directories.
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= 5.5.0.4433CVSS 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.
-
Locate Slmail installation and verify versionSearch for Slmail installation directories (common paths: C:\Program Files\Slmail, C:\Slmail) and check the executable or DLL version properties against 5.5.0.4433Affected if Slmail version is exactly 5.5.0.4433 and the program is installed
-
Confirm MailAdmin_dll.htm existsCheck for the presence of MailAdmin_dll.htm in the web root or admin directory of the Slmail installation (typically in a /mailadmin or /admin folder)Affected if MailAdmin_dll.htm file exists in the Slmail web directory
-
Verify web admin interface is accessibleAttempt to access the MailAdmin_dll.htm page via HTTP/HTTPS on the port Slmail web service runs (commonly port 8888, 8080, or 80)Affected if The web admin page is reachable over the network
-
Check if admin authentication is configuredInspect Slmail configuration files (slmail.ini, config.xml, or registry entries) for admin account settings and authentication statusAffected if An admin account exists and authentication is enabled for the web interface
-
Look for indicators of traversal access attemptsReview Slmail logs, web server logs, and system event logs for evidence of directory traversal patterns (multiple %2F, .. sequences) in requests to the dodoc parameterAffected if Log entries show traversal sequences in requests to MailAdmin_dll.htm
You are affected if Seattlelab Slmail version 5.5.0.4433 is installed, the MailAdmin_dll.htm web admin interface is exposed, and the system is network-accessible to authenticated users.
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 input validation and path normalization on the 'dodoc' parameter to prevent traversal sequences, ensuring paths are constrained to allowed directories and rejecting any input containing encoded or raw path traversal characters.
- 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-2023-4593 — 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-4593 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