CVE-2025-68723
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 · uneditedAxigen Mail Server before 10.5.57 contains multiple stored Cross-Site Scripting (XSS) vulnerabilities in the WebAdmin interface. Three instances exist: (1) the log file name parameter in the Local Services Log page, (2) certificate file content in the SSL Certificates View Usage feature, and (3) the Certificate File name parameter in the WebMail Listeners SSL settings. Attackers can inject malicious JavaScript payloads that execute in administrators' browsers when they access affected pages or features, enabling privilege escalation attacks where low-privileged admins can force high-privileged admins to perform unauthorized actions.
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 confidenceAxigen Mail Server before 10.5.57 has multiple stored XSS vulnerabilities in the WebAdmin interface where attackers can inject malicious JavaScript into three parameters: log file names, certificate file content, and certificate file names. These payloads execute when administrators access the affected pages, enabling privilege escalation from low-privileged to high-privileged admin accounts.
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>= 10.3.0, < 10.5.57>= 10.6.0, < 10.6.26CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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.
-
Check Axigen Mail Server versionLocate the installed Axigen Mail Server version using the system package manager, control panel, or by querying the service directly (e.g., axigen --version or checking the About section in WebAdmin)Affected if The installed version is >= 10.3.0 and < 10.5.57, OR >= 10.6.0 and < 10.6.26
-
Verify WebAdmin interface is accessibleConfirm the WebAdmin web interface is enabled and reachable (typically on ports 9000 or 9443 for HTTPS). Check service status or configuration files for WebAdmin listener settingsAffected if WebAdmin interface is enabled and exposed to the user population
-
Inspect log file name configurationAccess WebAdmin interface, navigate to Logging or Log Settings section, and examine the configured log file name parameter for any unexpected or suspicious valuesAffected if A non-admin or low-privileged user has previously configured log file names through the interface and the current admin views that configuration page
-
Inspect certificate file content configurationAccess WebAdmin interface, navigate to SSL/TLS or Certificate Settings section, and examine the certificate file content field for any injected script contentAffected if A non-admin or low-privileged user has previously uploaded or modified certificate file content and the current admin views that configuration page
-
Inspect certificate file name configurationAccess WebAdmin interface, navigate to SSL/TLS or Certificate Settings section, and examine the certificate file name field for any unexpected script-containing valuesAffected if A non-admin or low-privileged user has previously configured certificate file names with malicious payloads and the current admin views that configuration page
Your environment is affected if the installed Axigen Mail Server version falls within the vulnerable ranges AND the WebAdmin interface is accessible, allowing potential injection of malicious JavaScript into log file names, certificate file content, or certificate file name parameters.
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.
dbcve · scoped10.5.5710.6.26
Upgrade to Axigen Mail Server 10.5.57 or later. Until then, implement input validation and output encoding for the log file name, certificate file content, and certificate file name parameters in the WebAdmin interface.
10.5.57 (for versions 10.3.0-10.5.56) or 10.6.26 (for versions 10.6.0-10.6.25)
- 1. Identify the currently installed Axigen Mail Server version using the admin interface or command line
- 2. If running version 10.3.0 to 10.5.56, plan upgrade to version 10.5.57
- 3. If running version 10.6.0 to 10.6.25, plan upgrade to version 10.6.26
- 4. Create a complete backup of the Axigen configuration, including all settings, mail data, and certificate files
- 5. Download the appropriate fixed version (10.5.57 or 10.6.26) from the official Axigen website (www.axigen.com)
- 6. Review the Axigen upgrade documentation for version-specific migration instructions
- 7. Stop the Axigen services before performing the upgrade
- 8. Install the upgraded version following vendor-provided installation/upgrade procedures
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68723 — 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-2025-68723 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