CVE-2023-48974
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 · uneditedCross Site Scripting vulnerability in Axigen WebMail prior to 10.3.3.61 allows a remote attacker to escalate privileges via a crafted script to the serverName_input parameter.
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 confidenceCross-site scripting (XSS) vulnerability in Axigen WebMail's serverName_input parameter allows remote attackers to inject malicious scripts, which can be used to escalate privileges.
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.5.7CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 version of Axigen Mail Server (typically via admin interface, 'axigenctl version', or system information). Compare against the affected range: any version <= 10.5.7 is vulnerable.Affected if Installed version is 10.5.7 or lower
-
Verify WebMail interface is enabledConfirm that the Axigen WebMail service is running and accessible (check WebMail listener in admin panel or test connectivity to port 443/8080).Affected if WebMail interface is exposed and accessible to users or attackers
-
Confirm serverName_input parameter existsThe vulnerability resides in the 'serverName_input' parameter within WebMail. This parameter is used in WebMail configuration pages. Check if WebMail configuration allows setting a server name through this input field.Affected if WebMail is configured and the serverName_input parameter is present in the web interface
A user is affected if they are running Axigen Mail Server version 10.5.7 or lower with WebMail enabled and accessible.
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 · scopedUpgrade Axigen WebMail to version 10.3.3.61 or later. Additionally, implement proper input validation and output encoding on the serverName_input parameter to prevent XSS attacks.
Axigen Mail Server 10.3.3.61 or latest 10.x release (currently 10.5.8 or higher)
- 1. Navigate to the official Axigen download portal at www.axigen.com
- 2. Locate the Axigen Mail Server version 10.3.3.61 or later (preferably the latest 10.x release)
- 3. Download the appropriate installer for your operating system
- 4. Back up your current Axigen configuration and mail data
- 5. Stop the Axigen services
- 6. Install the new version over the existing installation
- 7. Start the Axigen services
- 8. Verify the WebMail interface loads correctly and the serverName_input parameter is no longer vulnerable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-48974 — 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-48974 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