Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-67824: n/a

0
Unknown
VulnerabilityCVE-2025-67824cvecve-2025-67824
Published: Tue Jan 20 2026 (01/20/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

The WorklogPRO - Jira Timesheets plugin in the Jira Data Center before 4.24.1-jira9, 4.24.1-jira10, and 4.24.1-jira11 allows attackers to inject arbitrary HTML or JavaScript via XSS. This is exploited via a crafted payload placed in the name of a filter. This code is executed in the browser when the user attempts to create a timesheet with the filter timesheet type on the custom timesheet dialog because the filter name is not properly sanitized during the action.

AI-Powered Analysis

AILast updated: 01/20/2026, 15:50:19 UTC

Technical Analysis

CVE-2025-67824 is a stored cross-site scripting (XSS) vulnerability affecting the WorklogPRO - Jira Timesheets plugin in Jira Data Center versions before 4.24.1-jira9, 4.24.1-jira10, and 4.24.1-jira11. The vulnerability arises because the plugin fails to properly sanitize the filter name input, allowing attackers to inject arbitrary HTML or JavaScript code. This malicious payload is stored in the filter name and executed in the victim's browser when they attempt to create a timesheet using the filter timesheet type on the custom timesheet dialog. The attack vector involves crafting a specially designed filter name containing the XSS payload. When a user interacts with the timesheet creation interface, the injected script runs with the user's browser privileges, potentially enabling session hijacking, credential theft, or further client-side attacks. The vulnerability does not require prior authentication to inject the payload, but user interaction is necessary to trigger the execution. There are no known public exploits at this time, but the risk remains significant given the widespread use of Jira Data Center in enterprise environments. The lack of a CVSS score necessitates a severity assessment based on the vulnerability's characteristics. The plugin versions affected are used in Jira Data Center, a product widely adopted by large organizations for issue tracking and project management, increasing the potential impact. The vulnerability highlights the importance of proper input validation and output encoding in web applications, especially in plugins that extend core enterprise software.

Potential Impact

For European organizations, this vulnerability poses a significant risk to confidentiality and integrity of user sessions and data within Jira Data Center environments. Successful exploitation could allow attackers to execute arbitrary scripts in the context of the victim's browser, leading to session hijacking, unauthorized actions, or data exfiltration. Given Jira's role in managing sensitive project and issue data, such attacks could disrupt business operations, leak confidential information, or facilitate further network intrusion. The impact is amplified in environments where multiple users have access to Jira and rely on the WorklogPRO plugin for timesheet management. Additionally, the vulnerability could be leveraged as a foothold for lateral movement within an organization's network. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers often weaponize such vulnerabilities once disclosed. European organizations with strict data protection regulations (e.g., GDPR) must consider the compliance implications of potential data breaches resulting from this vulnerability.

Mitigation Recommendations

Organizations should promptly update the WorklogPRO - Jira Timesheets plugin to version 4.24.1-jira9 or later, as these versions address the vulnerability by properly sanitizing filter names. Until updates can be applied, administrators should restrict access to the timesheet creation functionality or disable the plugin if feasible. Implementing web application firewalls (WAFs) with rules to detect and block suspicious input patterns related to filter names can provide temporary protection. Conduct thorough input validation and output encoding on all user-supplied data within custom plugins or integrations to prevent similar issues. Educate users about the risks of interacting with untrusted filters or timesheets and encourage vigilance against suspicious activity. Regularly audit Jira plugin versions and configurations to ensure they are up to date and securely configured. Monitoring logs for unusual filter creation or timesheet activity may help detect attempted exploitation. Finally, coordinate with Atlassian support and plugin vendors for timely security advisories and patches.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-12-12T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 696fa0dc4623b1157c3be2d5

Added to database: 1/20/2026, 3:35:56 PM

Last enriched: 1/20/2026, 3:50:19 PM

Last updated: 1/20/2026, 8:20:48 PM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats