Cyber Resilience

CVE-2026-25764

XSS in Openproject ≤ 16.6.7

Published
06 February 2026
Modified
13 February 2026
Patch / advisory
CVSS Score v3.1 3.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:L
EPSS Score 0.0024 15th percentile
Risk Priority 29 floored blend · peak EPSS

Summary

CVE-2026-25764 is a low-severity Basic XSS (CWE-80) vulnerability in Openproject Openproject. Its CVSS base score is 3.5 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-35224Same product: Openproject Openproject
CVE-2026-23625Same product: Openproject Openproject
CVE-2025-24892Same product: Openproject Openproject
CVE-2026-32703Same product: Openproject Openproject
CVE-2026-30235Same product: Openproject Openproject
CVE-2023-31140Same product: Openproject Openproject
CVE-2026-22602Same product: Openproject Openproject
CVE-2026-22600Same product: Openproject Openproject
CVE-2026-22604Same product: Openproject Openproject
CVE-2023-33960Same product: Openproject Openproject

Affected Assets

openproject
openproject
≤ 16.6.7 · 17.0.0 — 17.0.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.2.1
  • V1.3.1
  • V1.3.3
  • V1.3.4

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect neutralization of script tags through targeted XSS test cases.

Input validation explicitly requires checking and neutralizing untrusted web inputs containing script-related characters before they reach a downstream renderer.

Secure engineering principles include mandatory output encoding and neutralization of HTML metacharacters to stop injection at the source.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require output encoding and input validation that prevent basic XSS.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches unneutralized script tags before release.

prevents

Secure SDLC mandates input validation and output encoding that directly prevent basic XSS.

prevents

Application security requirements explicitly call for neutralization of script-related HTML tags.

prevents

Secure coding standards require proper escaping of <, >, & to block XSS.

none

Web filtering can block some reflected XSS payloads at the network edge.

References