# CVE-2025-24288: Hardcoded credentials in Director

> Attackers can gain privileged access to Versa Director using default credentials exposed on internet-facing services, requiring immediate password changes.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 18 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-rwr4-qw9c-fjxm

## What is CVE-2025-24288?

CVE-2025-24288 is a critical vulnerability in Versa Director, published on 18 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Versa Director software exposes a number of services by default and allow attackers an easy foothold due to default credentials and multiple accounts (most with sudo access) that utilize the same default credentials. By default, Versa director exposes ssh and postgres to the internet, alongside a host of other services.

Versa Networks is not aware of any reported instance where this vulnerability was exploited. Proof of concept for this vulnerability has been disclosed by third party security researchers.  

Workarounds or Mitigation: 

Versa recommends the following  security controls:

1) Change default passwords to complex passwords
2) Passwords must be complex with at least 8 characters that comprise of upper case, and lower case alphabets,  as well as at at least one digit, and one special character
3) Passwords must be changed at least every 90 days
4) Password change history is checked to ensure that the at least the last 5 passwords must be used when changing password.
5) Review and audit logs for all authentication attempts to check for unauthorized/suspicious login attempts and enforce remediation steps.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 1 product.


Products: Versa-Networks Versa Director.

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

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

## Is CVE-2025-24288 being exploited?

There is no known exploitation of CVE-2025-24288 in the wild and no public exploit code.

## Other vulnerabilities in Versa Director

- [CVE-2024-39717](https://insights.sbomify.com/CVE-2024-39717/): Versa Director Dangerous File Type Upload (medium 6.6, exploited in the wild)
- [CVE-2024-42450](https://insights.sbomify.com/CVE-2024-42450/): Hardcoded credentials in Director (critical 10.0)
- [CVE-2019-25029](https://insights.sbomify.com/CVE-2019-25029/): Command injection in Versa Director (critical 9.8)
- [CVE-2025-23173](https://insights.sbomify.com/CVE-2025-23173/): Information disclosure in Director (high 7.5)
- [CVE-2025-23171](https://insights.sbomify.com/CVE-2025-23171/): File upload in Director (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-24288 is a critical vulnerability in Versa Director, published on 18 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24288 in the wild and no public exploit code.

Affected product: Versa Director. 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-24288/ (Markdown: https://insights.sbomify.com/CVE-2025-24288/index.md)
```

## Sources

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

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