dbcve.org
SlmailApplication · Seattlelab

CVE-2023-4594

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Stored XSS vulnerability. This vulnerability could allow an attacker to store a malicious JavaScript payload via GET and POST methods on multiple parameters 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 confidence

A stored cross-site scripting (XSS) vulnerability exists in the MailAdmin_dll.htm file where malicious JavaScript payloads can be injected and persistently stored via multiple GET and POST parameters. When other users view the affected page, the stored script executes in their browsers, potentially allowing session hijacking, credential theft, or defacement.

MitigationImplement strict input validation and context-aware output encoding on all user-supplied parameters in MailAdmin_dll.htm, and deploy Content Security Policy (CSP) headers to mitigate XSS execution.

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
SlmailApplication
Affected:= 5.5.0.4433

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Slmail installation
    Locate the Seattlelab Slmail application on the system, typically installed in C:\Program Files\Slmail or similar directories. Check for the presence of the slmail.exe binary.
    Affected if Slmail version 5.5.0.4433 is installed on the system
  2. Verify the exact version number
    Right-click on slmail.exe, select Properties, and check the File Version in the Details tab. Alternatively, run 'slmail.exe -v' or check the About dialog within the application.
    Affected if The installed version is exactly 5.5.0.4433
  3. Locate MailAdmin_dll.htm
    Search the Slmail installation directory for the file MailAdmin_dll.htm. This file is typically found in the web admin or help documentation folders within the Slmail directory structure.
    Affected if The file MailAdmin_dll.htm exists in the Slmail installation directory
  4. Determine if web interface is accessible
    Check if the Slmail web administration interface is enabled and accessible. Typically accessed via browser on ports 8080 or 8888, or check the application configuration for web server settings.
    Affected if The web interface is enabled and MailAdmin_dll.htm can be accessed via HTTP
  5. Inspect stored XSS indicators
    If web logs or database backups are available, examine request logs for the MailAdmin_dll.htm page and look for suspicious patterns in GET/POST parameters that may contain script tags or HTML fragments.
    Affected if Malicious script payloads are found stored in web logs or configuration files related to MailAdmin_dll.htm parameters

A system is affected only if Seattlelab Slmail version 5.5.0.4433 is installed, the MailAdmin_dll.htm file exists, and the web interface is accessible, allowing the stored XSS to be triggered.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and context-aware output encoding on all user-supplied parameters in MailAdmin_dll.htm, and deploy Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix High confidence
  1. 1. Replace Slmail with a currently supported mail server solution (e.g., Microsoft Exchange, Postfix, MailEnable, or Alt-N MDaemon) that receives regular security updates.
  2. 2. If replacement is not immediately possible, restrict network access to the MailAdmin interface to trusted IPs only via firewall rules.
  3. 3. Implement input validation and output encoding on any web-facing interfaces if a custom solution is deployed.
  4. 4. Consider disabling the MailAdmin web interface entirely if not required for operations.
  5. 5. Monitor INCIBE and vendor communications for any future security updates.
Caveat Slmail is a legacy/discontinued product with no available security updates; migration to a supported mail server solution is required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Slmail Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4594 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4594 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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