CVE-2023-49101
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 · uneditedWebAdmin in Axigen 10.3.x before 10.3.3.61, 10.4.x before 10.4.24, and 10.5.x before 10.5.10 allows XSS attacks against admins because of mishandling of viewing the usage of SSL certificates.
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 confidenceA stored XSS vulnerability exists in Axigen's WebAdmin interface when viewing SSL certificate usage. The application fails to properly sanitize or encode input when displaying SSL certificate information, allowing an attacker to inject malicious JavaScript that executes in an administrator's browser session.
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.3.0, < 10.3.3.61>= 10.4.0, < 10.4.24>= 10.5.0, < 10.5.10CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Axigen installation and versionLocate the Axigen installation directory and check the version file or run 'axigen --version' if available. Common paths include /opt/axigen or C:\Program Files\Axigen.Affected if The installed version falls within 10.3.3.0 to 10.3.3.60, 10.4.0 to 10.4.23, or 10.5.0 to 10.5.9.
-
Confirm WebAdmin interface is enabledCheck the Axigen configuration file (typically axigen.cfg or via admin console) for WebAdmin service status. Look for webAdmin or webadmin service listening on ports like 8080 or 8443.Affected if WebAdmin interface is accessible and running.
-
Verify SSL certificate feature is accessibleLog into WebAdmin and navigate to the SSL certificate management or usage viewing section, typically found under Security or Settings menus.Affected if The SSL certificate usage viewing feature is available and accessible to administrators.
-
Check for existing SSL certificatesReview the SSL certificates configured in Axigen via the admin interface or configuration files in the certs directory.Affected if Any SSL certificates are configured and viewable through the WebAdmin interface.
You are affected if Axigen version is in the vulnerable ranges AND WebAdmin with SSL certificate viewing feature is 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 · scoped10.3.3.6110.4.2410.5.10
Upgrade to Axigen version 10.3.3.61, 10.4.24, or 10.5.10 or later to remediate this vulnerability. Until patched, restrict administrative access to trusted users only.
10.3.3.61 (or later 10.3.x), 10.4.24 (or later 10.4.x), or 10.5.10 (or later 10.5.x)
- Identify the currently installed Axigen version using the admin interface or system inventory
- Determine which version branch is in use (10.3.x, 10.4.x, or 10.5.x)
- Download the appropriate fixed version: upgrade to 10.3.3.61 or later for 10.3.x branch, 10.4.24 or later for 10.4.x branch, or 10.5.10 or later for 10.5.x branch
- Review the Axigen release notes for the target version to check for any prerequisites or migration requirements
- Back up the current Axigen configuration and data directories before proceeding with the upgrade
- Install the new version following the standard Axigen upgrade procedure
- Verify the WebAdmin interface is accessible and the SSL certificate viewing functionality works correctly
- Confirm the XSS vulnerability is remediated by reviewing that user input in SSL certificate usage view is properly sanitized
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-49101 — 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-49101 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