CVE-2023-41703VulnerabilityPublished 12 Feb 2024Updated 4 Nov 2025

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

Affects Open-Xchange OX App SuiteSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.1Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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 12 Feb 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 26 Oct 2026.

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

European organizations should implement the following specific mitigation steps: 1) Immediately apply the official patches or updates provided by Open-Xchange GmbH that address CVE-2023-41703 to ensure proper sanitization of user-generated content. 2) Enforce strict content security policies (CSP) in web browsers accessing OX App Suite to restrict script execution sources and reduce impact of potential XSS attacks. 3) Educate users about the risks of interacting with untrusted or unexpected documents and mentions, emphasizing caution with links or shared content in collaborative environments. 4) Monitor logs and user activity for unusual behavior related to document comments and mentions, including unexpected script execution or session anomalies. 5) Consider implementing web application firewalls (WAF) with rules tailored to detect and block malicious input patterns targeting OX App Suite. 6) Review and tighten access controls and session management policies to limit the impact of compromised sessions. 7) Regularly audit and update security configurations of OX App Suite deployments to align with vendor recommendations and security best practices. These measures, combined with patching, will reduce the likelihood and impact of exploitation.

Description

User ID references at mentions in document comments were not correctly sanitized. Script code could be injected to a users session when working with a malicious document. Please deploy the provided updates and patch releases. User-defined content like comments and mentions are now filtered to avoid potentially malicious content. No publicly available exploits are known.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to confidentiality and integrity of user sessions within OX App Suite environments. Successful exploitation could allow attackers to hijack user sessions, steal sensitive information such as emails or documents, or perform unauthorized actions under the victim's identity. This is particularly concerning for organizations relying on OX App Suite for internal communications, document collaboration, and email services, where exposure of sensitive business or personal data could lead to reputational damage, regulatory penalties under GDPR, and operational disruptions. The requirement for user interaction limits large-scale automated exploitation but targeted phishing or social engineering campaigns could leverage this vulnerability effectively. Since OX App Suite is used by various European enterprises, educational institutions, and public sector organizations, the impact could be significant if patches are not applied. The absence of known public exploits reduces immediate risk but should not lead to complacency. Attackers may develop exploits in the future, increasing the threat level. Additionally, the vulnerability's ability to affect multiple users through shared documents increases potential lateral movement within organizations.

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