Cyber Resilience

CVE-2026-68489

Published
14 September 2026
Modified
18 September 2026
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0040 34th percentile
Risk Priority 39 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-68489 is a high-severity Static Code Injection (CWE-96) vulnerability in Plesk (inferred from references). Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Embedded Payloads (T1027.009); ranked at the 34th 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 SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Static Code Injection in Plesk extensions "Ruby" before 1.6.6 and "Node.js Toolkit" before 2.5.0 allows remote authenticated users to execute arbitrary code as root via custom environment variables.

CWE(s)
CWE-96

Related Threats

MITRE ATT&CK Enterprise Techniques

T1027.009 Embedded Payloads Stealth
Adversaries may embed payloads within other files to conceal malicious content from defenses.
attack.mitre.org →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-13264Shared CWE-96
CVE-2024-13265Shared CWE-96
CVE-2025-30091Shared CWE-96
CVE-2023-39726Shared CWE-96
CVE-2024-0788Shared CWE-96
CVE-2025-57707Shared CWE-96
CVE-2024-13263Shared CWE-96
CVE-2025-36595Shared CWE-96
CVE-2024-13268Shared CWE-96
CVE-2025-7825Shared CWE-96

Affected Assets

Plesk
—
inferred from references and description; NVD did not file a CPE for this CVE

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.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation partial match

Developer testing and evaluation can discover missing neutralization of directives in saved code artifacts.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles include secure input handling and neutralization requirements that structurally avoid static injection.

SI-10 Information Input Validation partial match

Input validation directly stops unneutralized directives from being inserted into static code resources.

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 partial match
prevents

Secure SDLC practices directly require input neutralization to block static code injection into templates, configs, or libraries.

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.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and sanitization that directly prevents static code injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for neutralizing untrusted input before it is stored in executable resources.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce injection surfaces but do not prescribe the specific neutralization techniques.

A.8.28 Secure coding partial match
prevents

Secure coding explicitly requires proper neutralization of directives in templates, libraries and configuration files.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development and acceptance will detect static code injection but does not prevent it at the source.

A.8.32 Change management none match
mitigates

Change management can catch unsafe code changes but does not enforce input neutralization.

References