LiveActive security incident?Get immediate response
CVE Record

CVE-2023-40355: Cross Site Scripting (XSS) vulnerability in Axigen versions 10.3.3.0 before 10.3.3.59, 10.4.0 before 10.4.1...

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.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Axigen WebMail had a cross-site scripting issue in specific 10.3, 10.4, and 10.5 releases. An authenticated attacker could use the Standard/Ajax version-switching logic to run browser-side code and potentially access sensitive information. The public bundle does not show known active exploitation.

Executive priority

Treat as a routine but time-bound webmail security update. It is not marked as actively exploited in the provided sources, but exposed mail systems handle sensitive communications and should not remain on vulnerable versions.

Technical view

CVE-2023-40355 is CWE-79 XSS affecting Axigen 10.3.3.0 before 10.3.3.59, 10.4.0 before 10.4.19, and 10.5.0 before 10.5.5. CVSS 3.1 is 5.4: network reachable, low complexity, low privileges, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is likely limited to organizations running affected Axigen WebMail versions, especially internet-facing deployments with authenticated users. The provided affected CPE data is incomplete, so asset validation should rely on product inventory and Axigen version checks.

Exploitation context

The bundle identifies authenticated attacker requirements and user interaction, but does not provide KEV listing or cited evidence of active exploitation. The issue matters because webmail accounts often contain sensitive business communications and trusted user sessions.

Researcher notes

The NVD-style affected vendor/product fields in the bundle are not populated, while the description names Axigen version ranges. Avoid broad product claims beyond Axigen WebMail and the listed versions. User interaction and authentication requirements reduce severity but do not eliminate risk.

Mitigation direction

  • Upgrade Axigen 10.3.3.x to 10.3.3.59 or later.
  • Upgrade Axigen 10.4.x to 10.4.19 or later.
  • Upgrade Axigen 10.5.x to 10.5.5 or later.
  • Review Axigen vendor guidance for deployment-specific remediation details.
  • Restrict WebMail exposure where business requirements allow.

Validation and detection

  • Inventory Axigen WebMail servers and record exact installed versions.
  • Confirm no server runs the listed vulnerable version ranges.
  • Check whether WebMail is externally reachable or limited to trusted networks.
  • Review authentication logs for unusual WebMail activity around user sessions.
  • Confirm remediation against Axigen’s CVE advisory.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-40355 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-40355Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.