VulnerabilityPublished 26 Jan 2026Updated 27 Jan 2026

CVE-2025-70368: worklenz · Cross-site Scripting

Affects worklenzSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% 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 26 Jan 2026
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 or the CVSS exploit maturity 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
GitHubworklenz/worklenz`pkg:github/worklenz/worklenz`Other threats	Affected =2.1.5	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-70368, organizations should first verify if they are running Worklenz version 2.1.5 and prioritize upgrading to a patched version once available. In the absence of an official patch, implement strict input validation and output encoding on the Updates text field to sanitize user input and prevent script injection. Employ Content Security Policy (CSP) headers to restrict execution of unauthorized scripts in browsers. Educate users to be cautious when clicking links or viewing project updates, especially from untrusted sources. Limit privileges of users who can submit updates to reduce the attack surface. Monitor logs and user activity for suspicious behavior indicative of exploitation attempts. Consider deploying web application firewalls (WAFs) with rules targeting XSS payloads in the affected endpoints. Regularly review and update security policies related to web application usage and user-generated content. Coordinate with Worklenz vendor support for timely updates and advisories.

Description

CVE-2025-70368 is a medium-severity Stored Cross-Site Scripting (XSS) vulnerability found in Worklenz version 2.1.5, specifically in the Project Updates feature. An attacker can inject malicious JavaScript payloads into the Updates text field, which are then rendered unsanitized in the reporting view. This can lead to script execution in the browsers of users who view the affected page, potentially compromising confidentiality and integrity. Exploitation requires the attacker to have limited privileges and user interaction, as victims must visit the maliciously crafted page. No known exploits are currently reported in the wild. European organizations using Worklenz 2.1.5 should prioritize patching or applying mitigations to prevent potential exploitation.

Impact

For European organizations, exploitation of this vulnerability could lead to unauthorized disclosure of sensitive information and manipulation of data integrity through malicious script execution in users’ browsers. This is particularly concerning for organizations relying on Worklenz for project management and reporting, as attackers could hijack sessions, steal credentials, or perform actions on behalf of legitimate users. The requirement for limited privileges and user interaction reduces the ease of exploitation but does not eliminate risk, especially in environments with many users accessing project updates. The vulnerability could facilitate lateral movement or persistent footholds in corporate networks if combined with social engineering. Confidentiality breaches may expose sensitive project data, impacting competitive advantage and compliance with data protection regulations such as GDPR. Integrity impacts could undermine trust in project reporting and decision-making processes. Availability is not directly affected, but indirect effects could arise from follow-on attacks.

Summary

CVE-2025-70368 is a Stored Cross-Site Scripting (XSS) vulnerability affecting Worklenz version 2.1.5, a project management tool. The vulnerability resides in the Project Updates feature, where user-submitted content in the Updates text field is not properly sanitized before being displayed in the reporting view. This lack of input validation allows attackers to inject malicious JavaScript code that executes in the context of other users' browsers when they access the affected page. The vulnerability is classified under CWE-79, indicating improper neutralization of input during web page generation. The CVSS v3.1 base score is 5.4 (medium severity), with the vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, meaning the attack can be launched remotely over the network with low attack complexity, requires limited privileges, and user interaction is necessary. The scope is changed, indicating that the vulnerability affects resources beyond the initially vulnerable component. The impact affects confidentiality and integrity but not availability. No patches or exploits are currently publicly available, but the vulnerability is published and should be addressed promptly. Stored XSS can be leveraged for session hijacking, credential theft, or delivering further attacks such as phishing or malware distribution within an organization.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Feb 2026, 08:40 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats