VulnerabilityPublished 6 Feb 2026Updated 9 Feb 2026

CVE-2026-25764: opf openproject · Basic XSS

Affects opf openprojectSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low : upgrade to 17.0.3 or 16.6.7 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

3.5Low

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.0.3, 16.6.7

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

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

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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within 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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Feb 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

Upgrade openproject and opf/openproject to 17.0.3 or 16.6.7.

Affected software

Product	Affected	Fixed in
opfopenproject	Affected <17.0.3	Fixed in 17.0.3
opfopenproject	Affected <16.6.7	Fixed in 16.6.7
GitHubopf/openproject`pkg:github/opf/openproject`Other threats	Affected <16.6.7 <17.0.3	Fixed in 16.6.7 17.0.3

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

AI-suggested

European organizations should immediately upgrade OpenProject installations to versions 16.6.7 or 17.0.3 or later to apply the official patch. Beyond patching, organizations should enforce strict administrator access controls, including multi-factor authentication and regular credential audits, to reduce the risk of privilege misuse. Implement Content Security Policy (CSP) headers to limit the impact of potential XSS attacks by restricting script execution sources. Regularly review and sanitize user-generated content even if it originates from trusted roles to prevent injection of malicious code. Conduct security awareness training for administrators to recognize and avoid risky behaviors. Employ web application firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting OpenProject. Finally, monitor logs for unusual administrator activities or unexpected changes in work package names that could indicate exploitation attempts.

Description

OpenProject is an open-source, web-based project management software. Prior to versions 16.6.7 and 17.0.3, an HTML injection vulnerability occurs in the time tracking function of OpenProject. The application does not escape HTML tags, an attacker with administrator privileges can create a work package with the name containing the HTML tags and add it to the Work package section when creating time tracking. This issue has been patched in versions 16.6.7 and 17.0.3.

Impact

For European organizations, the impact of this vulnerability is generally low but not negligible. Since exploitation requires administrator privileges, the threat is mainly from insider attackers or compromised admin accounts. Successful exploitation could lead to injection of malicious scripts that might alter the integrity of project data or disrupt availability by causing UI or application malfunctions. However, there is no direct confidentiality breach. Organizations relying on OpenProject for critical project management and time tracking could face operational disruptions or trust issues if attackers manipulate displayed data or inject misleading content. The risk is higher in environments with weak internal access controls or where administrator credentials are insufficiently protected. Given the open-source nature of OpenProject, many European public sector and private organizations use it, so patching is essential to maintain operational integrity.

CWE-80Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.
Implementation
Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL…
Implementation · Output Encoding
Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8.
Implementation
With Struts, write all data from form beans with the bean's filter attribute set to true.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
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)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
V5.3.3 (opens in a new tab)
Attack patterns
XSS Targeting Non-Script Elements (opens in a new tab)
PHP Remote File Inclusion (opens in a new tab)
XSS Through HTTP Query Strings (opens in a new tab)
XSS Through HTTP Headers (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 14 Feb 2026, 12:13 UTC

WeaknessesCWE-80

Technical details

References

Community reviews

Related threats