# CVE-2025-65518: Denial of service in n/a

> Unauthenticated remote attackers can cause a persistent denial of service in Plesk Obsidian by sending crafted requests to the password endpoint.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-pgxq-gj96-mq7g

## What is CVE-2025-65518?

CVE-2025-65518 is a high-severity denial of service vulnerability in n/a, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Plesk Obsidian versions 8.0.1 through 18.0.73 are vulnerable to a Denial of Service (DoS) condition. The vulnerability exists in the get_password.php endpoint, where a crafted request containing a malicious payload can cause the affected web interface to continuously reload, rendering the service unavailable to legitimate users. An attacker can exploit this issue remotely without authentication, resulting in a persistent availability impact on the affected Plesk Obsidian instance.

Weakness: CWE-606 (Unchecked Input for Loop Condition), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-65518?

It affects 1 product.


Products: Webpros Plesk Obsidian.

## How do I fix CVE-2025-65518?

No fix has been published for CVE-2025-65518 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-65518 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65518 exists.

Public exploit code:

- Denial of Service Vulnerability in Plesk Obsidian via `get_password.php` (github_poc): https://github.com/Jainil-89/CVE-2025-65518

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-65518 and fix it if it is affected.

What it is: CVE-2025-65518 is a high-severity denial of service vulnerability in n/a, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65518 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-65518/ (Markdown: https://insights.sbomify.com/CVE-2025-65518/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-65518
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-65518
- OSV: https://osv.dev/vulnerability/CVE-2025-65518

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-65518/
Summaries are generated and may contain mistakes; the official description above is the record.