☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
[ VENDOR STATS ]
CVSS: 9.9 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H 🐛 CWE-36
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2026-68487

CVE-2026-68487 Path Traversal in Plesk
📅 PUBLISHED: 2026-09-10 00:00 UTC 🔄 UPDATED: 2026-09-22 10:15 UTC
[ ZERO-DAY / UNPATCHED ] [ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
VULNERABLE: UNKNOWN — no confirmed affected version range from any tracked source
CVSS VECTOR BREAKDOWN 9.9
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: L Privileges Required Low
UI: N User Interaction None
S: C Scope Changed
C: H Confidentiality High
I: H Integrity High
A: H Availability High
9.9
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2026-68487 is a path traversal vulnerability (CWE-36 — Absolute Path Traversal) in the Plesk Backup Manager component that allows an authenticated, low-privileged customer account to write arbitrary files with root-level privileges. The vulnerability carries a CVSS 3.0 base score of 9.9 (Critical), reflecting network reachability, low attack complexity, low privilege requirements, no user interaction, and a scope change with high confidentiality, integrity, and availability impact. Because Plesk is a widely deployed hosting control panel, any provider that grants customer-level access to the Backup Manager may be exposed; no public proof-of-concept, Nuclei template, or exploit code was identified at the time of writing, and no patch has been confirmed by any tracked source.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Technical Analysis

CWE-36 describes "Absolute Path Traversal," a weakness in which user-supplied input is used to construct a file path without adequately neutralizing absolute path sequences or traversal components. In CVE-2026-68487, the affected component is Plesk's Backup Manager. Per the NVD description, the flaw results in arbitrary file write as root by an authenticated customer.

The relevant dimensions of this weakness class are:

  • Attack vector (AV:N): The vulnerable interface is reachable over the network. Plesk control panels are typically exposed on HTTPS (port 8443 for the panel UI in common deployments), so an attacker does not require local access to the host.
  • Privileges required (PR:L): The attacker must hold a valid authenticated account, but only at the customer (low-privilege) level. The attacker does not need administrative panel access — the flaw converts a customer-level session into a root-level write primitive.
  • User interaction (UI:N): No other user must be tricked into an action.
  • Scope (S:C): The vulnerable component (Backup Manager, running within the panel's web/handler context) does not contain the impact — the impact escapes the security authority of the exploited component because the file is written with root privileges on the underlying operating system.
  • Confidentiality / Integrity / Availability (C:H/I:H/A:H): Arbitrary file write as root is effectively equivalent to full system compromise on a POSIX host. Integrity is fully compromised (any file can be overwritten), availability is fully compromised (system files, service binaries, or configuration can be destroyed or corrupted), and confidentiality is fully compromised (existing files can be overwritten or exfiltrated indirectly through subsequent system behavior).

The core mechanism — consistent with the CWE-36 classification and the NVD description — is that the Backup Manager processes a path value supplied by the authenticated customer, and insufficient validation permits an absolute path or traversal sequence to be resolved outside the intended backup directory. Because the resulting file operation executes with root privileges (the privilege level of the Plesk backend / privileged helper that performs backup file operations), the write is not constrained to the customer's own webspace or backup storage location.

Technical detail limitation: The provided intelligence (NVD description, CNA title, CWE, CVSS vector) does not specify the exact HTTP endpoint, request parameter, API method, or file-system path involved. No function names, endpoints, or parameter names are available, and none are invented here. The precise resolution logic (e.g., whether an absolute path is accepted directly, or a traversal sequence like ../ is used to escape a base directory) cannot be determined from the available data. Analysis is therefore conducted at the vulnerability-class level: inadequate path-canonicalization validation on a privileged backup file operation, reachable by a low-privileged authenticated user.

Exploitation Scenarios

No public proof-of-concept, exploit code, or Nuclei template was identified for CVE-2026-68487. The attack chain below is inferred strictly from the vulnerability class (CWE-36, absolute path traversal leading to arbitrary file write as root) and the NVD description. No specific endpoints, parameters, function names, or file paths are asserted because none are provided in the source data.

  1. Reconnaissance / target identification. The attacker identifies an internet- or intranet-exposed Plesk instance (commonly reachable on the panel HTTPS interface). From the Shodan dorks above, exposed panels can be enumerated by HTTP title/body content ("Plesk"). The attacker must obtain or already possess a valid customer-level account — for example, a legitimate but low-privileged hosting customer, a compromised customer credential set, or an account provisioned through a reseller. Administrative panel access is explicitly not required.

  2. Triggering the flaw class. After authenticating at the customer level, the attacker interacts with the Backup Manager feature. The vulnerability class is triggered when the Backup Manager accepts a path value influenced by the customer and fails to properly neutralize absolute-path or traversal content before using it in a file operation. In an absolute path traversal (CWE-36), the attacker supplies an absolute path (or a value that resolves to one), causing the file operation to target a location outside the intended backup directory. Because the operation runs with root privileges, the write is performed with the privileges of the Plesk backend/helper rather than the customer.

  3. Payload / execution method (vulnerability-class level). Arbitrary file write as root is a powerful primitive. At the class level — without asserting specific file paths — a root-level arbitrary write enables an attacker to:

    • Overwrite configuration files that privileged services later read.
    • Place files that the operating system or panel services will execute or load on restart or on a scheduled trigger.
    • Replace or corrupt binaries/scripts referenced by root-owned processes.

    These are standard consequences of a root-context arbitrary file write; the exact file(s) an attacker would target depend on the Plesk installation, which is not specified in the available data. No specific technique (e.g., a particular config file or scheduled task) is asserted here because the intelligence does not identify them.

  4. Post-exploitation impact. With the arbitrary root-context write established, the attacker can escalate from a low-privileged customer account to control over the Plesk host. CVSS scope-change (S:C) and full C/I/A impact capture this: the customer-level authority is fully bypassed, and the impact extends to the underlying OS. Consequences include tampering with other tenants' data, persistence, data destruction (A:H), and potential lateral movement to other services hosted on the same node.

Caveat: Because no exploit exists publicly and no specific request format is documented, an actual reproduction chain cannot be written with confidence. The steps above describe the class-level attack mechanism only.

Impact Assessment

Business impact. Plesk is a multi-tenant hosting control panel. A customer-to-root escalation in the Backup Manager affects every tenant and service managed by that panel instance, not just the attacker's own subscription. The blast radius is the entire managed server: hosted websites, mail, databases, DNS, and any co-located customer data. For hosting providers and MSPs, this translates to a provider-level breach affecting downstream customers, with associated regulatory, contractual, and reputational consequences.

CVSS subscore interpretation (9.9, Critical):

  • AV:N — remotely reachable.
  • AC:L — low complexity; the weakness class does not require special conditions.
  • PR:L — requires a valid customer-level account (the one meaningful barrier).
  • UI:N — no victim interaction.
  • S:C — impact escapes the vulnerable component (customer webspace → root/OS).
  • C:H/I:H/A:H — arbitrary root-context file write implies full compromise of confidentiality, integrity, and availability.

Prioritization. A base score of 9.9 places this in the critical tier. The EPSS score is not yet available (not scored by FIRST.org at time of writing; no value is fabricated here). CISA KEV status is NO — there is no evidence this CVE is being exploited in the wild as of this writing. The combination of "unpatched" (patch confidence 0/4) and "high impact" makes this a high-priority defensive item even absent known exploitation: defenders should assume exploit development is feasible and act on mitigation.

Detection Guidance

Because no specific endpoint or parameter is documented, the rules below target the vulnerability class — suspicious path-traversal or absolute-path content submitted to the Plesk Backup Manager interface — and should be tuned to each environment. These detections are heuristic and may require allowlisting of legitimate backup operations.

Sigma Rule

title: Potential Plesk Backup Manager Path Traversal / Absolute Path Abuse (CVE-2026-68487)
id: 8f2c1a4e-plesk-backup-traversal-cve202668487
status: experimental
description: Detects HTTP requests to the Plesk Backup Manager containing absolute-path or directory traversal sequences, consistent with CWE-36 exploitation attempts against an authenticated customer interface.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-68487
author: valtersit.com Threat Intelligence
date: 2026/01/01
logsource:
  category: webserver
  product: plesk
detection:
  selection_method:
    cs-method:
      - POST
      - PUT
  selection_uri:
    cs-uri-stem|contains:
      - '/backup'
      - '/BackupManager'
  selection_traversal:
    cs-uri-query|contains:
      - '../'
      - '..%2f'
      - '..%5c'
      - '%2e%2e%2f'
      - '%2e%2e/'
  selection_absolute:
    cs-uri-query|re:
      - '(?i)(file|path|location|target)=([a-z]:\\|/etc/|/root/|/usr/|/var/|/bin/|/sbin/)'
  condition: selection_method and selection_uri and (selection_traversal or selection_absolute)
fields:
  - c-ip
  - cs-method
  - cs-uri-stem
  - cs-uri-query
  - cs-username
falsepositives:
  - Legitimate backup configuration specifying absolute storage paths
  - Administrative backup operations
level: high
tags:
  - attack.t1190
  - cve.2026.68487

YARA Rule

rule CVE_2026_68487_Plesk_Backup_Traversal
{
    meta:
        description = "Detects path traversal / absolute path payloads targeting Plesk Backup Manager in captured HTTP traffic or logs (CVE-2026-68487)"
        author = "valtersit.com Threat Intelligence"
        reference = "https://nvd.nist.gov/vuln/detail/CVE-2026-68487"
        date = "2026-01-01"
        severity = "high"

    strings:
        $traversal1 = "../../" ascii nocase
        $traversal2 = "..\\..\\" ascii nocase
        $traversal3 = "%2e%2e%2f" ascii nocase
        $traversal4 = "..%2f" ascii nocase

        $backup1 = "BackupManager" ascii nocase
        $backup2 = "/backup" ascii nocase
        $backup3 = "plesk" ascii nocase

        $abs_unix1 = "/etc/" ascii
        $abs_unix2 = "/root/" ascii
        $abs_win1 = ":\\" ascii
        $abs_win2 = "C:\\" ascii

    condition:
        (uint16(0) == 0x4854 or true) and
        any of ($backup*) and
        ( any of ($traversal*) or any of ($abs_*) )
}

Suricata IDS Rule

alert http any any -> any any (msg:"CVE-2026-68487 Plesk Backup Manager Path Traversal Attempt"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/backup"; nocase; http.uri; content:"../"; nocase; http.uri; pcre:"/(%2e%2e%2f|\.\.%2f|\.\.\/)/i"; classtype:attempted-admin; reference:cve,2026-68487; reference:url,nvd.nist.gov/vuln/detail/CVE-2026-68487; sid:2026684870; rev:1; metadata:created_at 2026_01_01, updated_at 2026_01_01;)

alert http any any -> any any (msg:"CVE-2026-68487 Plesk Backup Manager Absolute Path Abuse"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/backup"; nocase; http.uri; pcre:"/(file|path|target|location)=([a-z]:(\\\\|\/)|%2fetc%2f|%2froot%2f)/i"; classtype:attempted-admin; reference:cve,2026-68487; sid:2026684871; rev:1;)

Elastic Detection

sequence by source.ip with maxspan=1m
  [ network where network.protocol == "http" and
      http.request.method in ("POST", "PUT") and
      wildcard(url.path, "*backup*") ]
  [ network where network.protocol == "http" and
      ( wildcard(url.query, "*../*") or wildcard(url.query, "*..%2f*") or wildcard(url.query, "*%2e%2e*") or
        wildcard(url.query, "*/etc/*") or wildcard(url.query, "*/root/*") ) ]

Splunk SPL Query

index=web OR index=proxy sourcetype IN (access_combined, "stream:http", plesk:access)
| eval uri = coalesce(uri, url, cs_uri_stem)
| eval qs  = coalesce(uri_query, cs_uri_query, "")
| where (match(uri, "(?i)backup"))
     AND (match(qs, "(?i)(\.\./|\.\.%2f|%2e%2e%2f|\.\.\\\\)")
          OR match(qs, "(?i)(file|path|target|location)=(/[a-z]+/|[a-zA-Z]:\\\\)"))
| stats count values(uri) as uris values(qs) as queries by src_ip, dest_ip, user
| sort - count

Wazuh OSSEC Rule

<group name="plesk,web,attack,">
  <rule id="2026687" level="12" frequency="1" timeframe="60">
    <if_matched_sid>31108</if_matched_sid>
    <match>backup</match>
    <regex>\.\./|\.\.%2f|%2e%2e%2f|\.\.\\</regex>
    <description>CVE-2026-68487: Possible Plesk Backup Manager path traversal attempt (CWE-36)</description>
    <mitre>
      <id>T1190</id>
    </mitre>
    <group>cve_2026_68487,</group>
  </rule>

  <rule id="2026688" level="12" frequency="1" timeframe="60">
    <if_matched_sid>31108</if_matched_sid>
    <match>backup</match>
    <regex>(file|path|target|location)=([a-zA-Z]:\\|/etc/|/root/|/usr/|/var/)</regex>
    <description>CVE-2026-68487: Plesk Backup Manager suspicious absolute path parameter</description>
    <mitre>
      <id>T1190</id>
    </mitre>
    <group>cve_2026_68487,</group>
  </rule>
</group>

Mitigation & Patch Guidance

Patch confidence: 0/4 (UNPATCHED — no patch evidence from any tracked source). At the time of writing, no vendor fix, workaround, or advisory was identified in the tracked sources. No affected-version range has been confirmed. The following measures are defensive-engineering controls and do not constitute a patch.

1) Immediate mitigations.

  • Restrict network exposure of the Plesk panel interface (commonly HTTPS on port 8443) to trusted management networks or VPN. Do not expose the panel directly to the internet if avoidable.
  • Enforce least privilege on Plesk customer accounts: audit which customers can access the Backup Manager and remove Backup Manager access from untrusted or external accounts where feasible.
  • Deploy a web application firewall (WAF) in front of the Plesk panel with rules that reject requests to Backup Manager endpoints containing directory-traversal sequences (../, encoded variants) or absolute-path values in path/parameter fields.
  • Ensure strong unique credentials and MFA for all Plesk accounts to reduce the likelihood that a customer-level account is compromised (PR:L requires an authenticated account).
  • Monitor and enable the detection rules in this report; log all Backup Manager activity centrally.

2) Patch / upgrade steps.

  • No patch exists per tracked sources. Monitor the Plesk / Web Pros official security advisories and the NVD entry (https://nvd.nist.gov/vuln/detail/CVE-2026-68487) for a vendor fix. When released, apply it immediately and verify the affected version range.
  • Do not rely on version-based detection alone until the vendor confirms the affected range, as no range is currently published.

3) Long-term hardening.

  • Run the Plesk panel and all backend/helper services with the minimum privileges necessary; where possible, avoid root-context file operations that accept user-influenced paths.
  • Implement file-integrity monitoring (FIM) on Plesk and OS-critical paths to detect unauthorized writes.
  • Apply network segmentation so that a compromised hosting node cannot reach unrelated management infrastructure.
  • Maintain an inventory of exposed management panels and continuously scan for panel exposure (see Shodan dorks) to shrink attack surface.
  • Adopt a routine patch cadence for control panels and treat any customer-to-root privilege boundary as high-risk.

References

Exploit-in-the-wild status: None disclosed. No public PoC, exploit code, or Nuclei template identified. CISA KEV status: NO. No threat-actor campaign attribution is available for this CVE.

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

product:"Plesk"
title:"Plesk"
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2026-68487/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.