dbcve.org
Axigen Mobile WebmailApplication · Axigen

CVE-2023-40355

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-07
Fix available
A fix is available. Upgrade to 10.3.3.59 / 10.4.19 or later.
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
Cross Site Scripting (XSS) vulnerability in Axigen versions 10.3.3.0 before 10.3.3.59, 10.4.0 before 10.4.19, and 10.5.0 before 10.5.5, allows authenticated attackers to execute arbitrary code and obtain sensitive information via the logic for switching between the Standard and Ajax versions.

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 confidence

Cross-site scripting (XSS) vulnerability in Axigen mail server's web interface version switching logic between Standard and Ajax modes. Authenticated attackers can inject malicious scripts through this mechanism to execute arbitrary code in user sessions and obtain sensitive information.

MitigationUpdate Axigen to version 10.3.3.59, 10.4.19, or 10.5.5 or later to apply the security patch. Limit administrative interface access to trusted users only until the patch can be deployed.

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
Axigen Mobile WebmailApplication
Affected:>= 10.3.3.0, < 10.3.3.59>= 10.4.0, < 10.4.19>= 10.5.0, < 10.5.5

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. Verify Axigen is installed
    Look for Axigen processes running on the system (e.g., using task manager, ps, or netstat to check for listening ports typically used by Axigen: 80, 443, 7000, 7070). Check for Axigen installation directories.
    Affected if Axigen mail server is running and accessible on the system
  2. Identify the installed Axigen version
    Access the admin interface or run the version check command provided by Axigen (such as 'axigen --version' or check the About section in the admin panel). Look for version files in the installation directory.
    Affected if The installed version cannot be determined or is not visible
  3. Confirm Mobile Webmail component is enabled
    Check the Axigen webmail configuration settings. Access the admin interface and navigate to the webmail settings or Mobile Webmail configuration to verify if this component is active.
    Affected if Mobile Webmail is enabled and accessible to users
  4. Compare version against affected ranges
    Match your installed version to these vulnerable ranges: 10.3.3.0 through 10.3.3.58; 10.4.0 through 10.4.18; 10.5.0 through 10.5.4. Any version within these ranges is affected.
    Affected if The installed version falls within any of these ranges: >= 10.3.3.0 and < 10.3.3.59, or >= 10.4.0 and < 10.4.19, or >= 10.5.0 and < 10.5.5

You are affected if Axigen Mobile Webmail is running and its version falls within the vulnerable ranges: 10.3.3.0-10.3.3.58, 10.4.0-10.4.18, or 10.5.0-10.5.4.

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
Upgrade available Upgrade to 10.3.3.59 / 10.4.19 / 10.5.5 or later
Fixed in 10.3.3.5910.4.1910.5.5
Interim mitigation

Update Axigen to version 10.3.3.59, 10.4.19, or 10.5.5 or later to apply the security patch. Limit administrative interface access to trusted users only until the patch can be deployed.

Recommended fix High confidence

Upgrade to 10.3.3.59 (or later 10.3.x), 10.4.19 (or later 10.4.x), or 10.5.5 (or later 10.5.x) depending on your current branch

  1. 1. Identify the currently installed Axigen Mobile Webmail version by checking the administration interface or running: axigen --version
  2. 2. Determine which version branch (10.3.x, 10.4.x, or 10.5.x) the current installation is on
  3. 3. For 10.3.x branch users: Upgrade to version 10.3.3.59 or later
  4. 4. For 10.4.x branch users: Upgrade to version 10.4.19 or later
  5. 5. For 10.5.x branch users: Upgrade to version 10.5.5 or later
  6. 6. Download the appropriate upgrade package from the official Axigen website (www.axigen.com)
  7. 7. Back up the current configuration and data before upgrading
  8. 8. Run the upgrade installer following Axigen's standard upgrade procedure
Caveat Review Axigen release notes for your target version to check for any changes in configuration syntax or feature behavior between your current and target version

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

Fix this in Axigen Mobile Webmail Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40355 — 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-40355 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