CVE-2026-48614
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn improper authorization vulnerability in the Plesk XML API allows an authenticated user to inject arbitrary configuration directives, resulting in arbitrary file write as root and full privilege escalation on the underlying server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an improper authorization vulnerability in Plesk's XML API where authenticated users can inject arbitrary configuration directives. This leads to arbitrary file write as root, enabling full privilege escalation to the underlying server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Plesk installation and versionRun 'plesk version' via SSH or check the Plesk admin interface for the version number. Document the exact version installed.Affected if The installed Plesk version falls within the range of versions affected by CVE-2026-48614 (check against official Plesk security advisories for the specific vulnerable version range).
-
Confirm XML API endpoint is enabledAccess the Plesk XML API endpoint (typically at /enterprise/control/agent.php or /api/v2/) or check the Plesk service configuration. Verify whether the XML API service is active and listening.Affected if The XML API is enabled and accessible on the server.
-
Check XML API access controlsReview Plesk's server settings, specifically the 'API' or 'XML API' permissions in the Plesk control panel. Look for whether IP access restrictions are applied or if the API is open to all IPs.Affected if The XML API is accessible without strict IP restrictions or is exposed to untrusted networks.
-
Inspect for existing unauthorized configurationsReview Plesk configuration files (located in /usr/local/psa or similar paths) and examine recent log entries in /var/log/plesk/ for suspicious XML API usage patterns or unexpected configuration directives.Affected if Unexpected configuration changes or suspicious XML API activity is present in logs.
Your environment is affected if Plesk with an unpatched version is running with the XML API enabled and accessible, allowing authenticated users to potentially inject arbitrary configuration directives.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the official Plesk patch/updates immediately and restrict XML API access to only necessary, trusted IP addresses or disable it if unused.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-48614 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data