CVE-2023-41710VulnerabilityPublished 8 Jan 2024Updated 4 Nov 2025

CVE-2023-41710: Open-Xchange OX App Suite · Cross-site Scripting

Affects Open-Xchange OX App SuiteSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Open-Xchange GmbH OX App Suite	Affected =0	Fixed in–

AI-suggested

Organizations should immediately ensure that their OX App Suite installations are updated with the vendor's latest patches that implement proper sanitization of user-supplied content. Beyond patching, administrators should audit and restrict the ability of users to input scriptable content, especially in fields related to URLs or HTML content. Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts within the application domain. Conduct regular security reviews of user input handling and output encoding mechanisms to detect and remediate similar injection flaws. Educate users about phishing and social engineering tactics that could lead to exploitation of stored XSS vulnerabilities. Monitor logs and user activity for suspicious behavior indicative of XSS exploitation attempts. If feasible, isolate or sandbox components that handle user-generated content to limit the impact of potential script execution. Finally, coordinate with the vendor for ongoing updates and advisories related to OX App Suite security.

Description

User-defined script code could be stored for a upsell related shop URL. This code was not correctly sanitized when adding it to DOM. Attackers could lure victims to user accounts with malicious script code and make them execute it in the context of a trusted domain. We added sanitization for this content. No publicly available exploits are known.

Impact

For European organizations using OX App Suite, this vulnerability poses a moderate risk primarily to confidentiality and integrity. Exploitation could allow attackers to execute arbitrary scripts in the context of the trusted domain, potentially leading to session hijacking, unauthorized actions, or data leakage within the application. This could compromise sensitive user data or internal communications managed through the suite. While availability is not impacted, the breach of confidentiality and integrity could disrupt business operations and damage trust. Given that OX App Suite is widely used by European enterprises and service providers for email and collaboration, the vulnerability could affect a broad user base. Attackers might leverage this flaw to target high-value accounts or pivot within networks. The requirement for user interaction and low privileges reduces the likelihood of mass exploitation but does not eliminate targeted attacks. Organizations handling sensitive communications or regulated data should consider this a significant concern and act promptly to remediate.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 18:39 UTC

Technical details

References

Community reviews

Related threats