CVE-2026-68489
CVE-2026-68489 — Static Code Injection in Plesk extensions "Ruby" before 1.6.6 and "Node.js Toolkit" before 2.5.0 allows remote authenticated users to…
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.
Published Updated Sources: NVD, WebPros (CNA), GitHub, GitHub Security Advisory, Red Hat (VEX), SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
8.7
high · 2 sources
Remediation
The vendor's own words where we have them.
Upgrade Plesk extension "Ruby" to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
Red Hat VEX · CVE-2026-68489
none_available: Affected
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| WebPros | Plesk extension "Ruby" | 0 to < 1.6.6 | Vulnerable |
| WebPros | Plesk extension "Node.js Toolkit" | 0 to < 2.5.0 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Attack Complexity
Low
Attack Vector
Network
Privileges Req
Low
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 8.7 | CVSS 4.0 | high | — | — | WebPros (CNA) |
| 8.8 | CVSS 3.1 | high | — | — | Red Hat (VEX) |
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-96 · Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')
- Read Files or Directories
- Read Application Data
- Bypass Protection Mechanism
- Gain Privileges or Assume Identity
Mitigation: Assume all input is malicious. Use an accept known good input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, boat may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as red or blue. Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
Weakness & attack patterns
- CWE-96
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1027.006Obfuscated Files or Information: HTML Smuggling
- T1027.009Obfuscated Files or Information: Embedded Payloads
- T1564.009Hide Artifacts: Resource Forking
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Prioritize edge telemetry for network-reachable Plesk extension "Ruby", Plesk extension "Node.js Toolkit".
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 8.7 (AV:N)
Sep 14, 2026 · NVD
Initial · CVE published
Sep 14, 2026 · NVD
Added · GHSA-vqcw-x7vm-9wwm published (high)
Sep 14, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 14, 2026 · SOCRadar CTI
References
6 on the record
- support.plesk.com/hc/en-us/articles/43473204617239
Vendor Advisory
- nvd.nist.gov/vuln/detail/CVE-2026-68489
NVD
- github.com/advisories/GHSA-vqcw-x7vm-9wwm
Exploit, Third Party Advisory
- access.redhat.com/security/cve/CVE-2026-68489
Vendor Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2533442
Vendor Advisory
- www.cve.org/CVERecord?id=CVE-2026-68489
Vendor Advisory
Elsewhere on this site
- WebProsevery CVE for this vendor
- Remote Code Execsame class
- CWE-96other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-68489 is Static Code Injection in Plesk extensions "Ruby" before 1.6.6 and "Node.js Toolkit" before 2.5.0 allows remote authenticated users to…, a high vulnerability affecting Plesk extension "Ruby", Plesk extension "Node.js Toolkit" from WebPros. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-68489. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-68489. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.7 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.