VulnerabilityPublished 3 Jul 2025

CVE-2025-49618: Plesk Obsidian · Resource Leak

Affects Plesk ObsidianSource CVE Database V5

Not known to be exploited · CVSS 5.8 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Plesk Obsidian	Affected =18.0.69	Fixed in–

AI-suggested

Immediate mitigation steps include restricting access to the /login_up.php endpoint through network-level controls such as firewall rules or web application firewalls (WAFs) to block unauthenticated requests. Organizations should audit their Plesk installations to identify affected versions and upgrade to a patched version once available from Plesk. In the absence of an official patch, temporarily disabling or restricting the vulnerable endpoint may be necessary. Additionally, organizations should rotate AWS credentials that may have been exposed to prevent unauthorized access. Implementing strict IAM policies with least privilege principles and enabling AWS CloudTrail logging and monitoring can help detect suspicious activities stemming from compromised credentials. Regular security assessments and penetration testing focused on web management interfaces are recommended to identify similar exposure risks. Finally, organizations should monitor threat intelligence feeds for any emerging exploit attempts targeting this vulnerability.

Description

In Plesk Obsidian 18.0.69, unauthenticated requests to /login_up.php can reveal an AWS accessKeyId, secretAccessKey, region, and endpoint.

Impact

For European organizations using Plesk Obsidian 18.0.69, this vulnerability poses a significant risk to the confidentiality of their AWS cloud credentials. Unauthorized disclosure of AWS access keys can lead to unauthorized access to cloud infrastructure, enabling attackers to exfiltrate sensitive data, deploy malicious workloads, or disrupt services indirectly. Given the widespread adoption of AWS in Europe and the popularity of Plesk as a hosting management tool, organizations could face compliance risks under GDPR if personal data is exposed or compromised. Additionally, the potential misuse of cloud resources could lead to financial losses due to resource abuse or ransom demands. The vulnerability's unauthenticated nature increases the risk of automated scanning and exploitation attempts, especially targeting hosting providers and enterprises relying on Plesk for cloud integration. This could also impact managed service providers (MSPs) who use Plesk to manage multiple client environments, amplifying the scope of potential damage.

CWE-402Transmission of Private Resources into a New Sphere ('Resource Leak') (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product makes resources available to untrusted parties when those resources are only intended to be accessed by the product.
OWASP Cheat Sheets
Authorization (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 12:54 UTC

WeaknessesCWE-402

Technical details

References

Community reviews

Related threats