CVE-2026-44962
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2026-44962 is a critical-severity XPath Injection (CWE-643) vulnerability in Plesk (inferred from references). Its CVSS base score is 9.9 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 50th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-33344
Vulnerability Data
Plesk contains an XPath injection vulnerability in the APS Application Catalog search functionality, where user-supplied input is interpolated into XPath queries without proper sanitization. This allows an authenticated, low-privileged user to execute arbitrary operating system commands on the server, resulting…
more
in local privilege escalation.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.4V1.2.7V2.2.1V4.3.1
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly requires neutralizing untrusted data before it is used to build XPath queries.
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.
Secure SDLC practices directly require input neutralization and query parameterization that prevent XPath injection.
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.
Secure coding standards require proper neutralization of untrusted input in XPath expressions.
Security testing in development catches XPath injection vulnerabilities before release.
Secure SDLC mandates input validation and query parameterization that directly prevent XPath injection.
Application security requirements explicitly call for defenses against injection flaws including XPath injection.
Secure architecture principles reduce the likelihood of unsafe dynamic query construction.
Vulnerability management processes identify and remediate XPath injection flaws discovered post-deployment.