# CVE-2025-23168: Security feature bypass in Director

> Attackers can bypass 2FA by redirecting OTPs or reusing codes, leading to account takeover in Versa Director SD-WAN platforms.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-p4f9-mqjc-2hrf

## What is CVE-2025-23168?

CVE-2025-23168 is a medium-severity vulnerability in Versa Director, published on 18 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Versa Director SD-WAN orchestration platform implements Two-Factor Authentication (2FA) using One-Time Passcodes (OTP) delivered via email or SMS. Versa Director accepts untrusted user input when dispatching 2FA codes, allowing an attacker who knows a valid username and password to redirect the OTP delivery (SMS/email) to their own device. OTP/TOTP codes are not invalidated after use, enabling reuse by an attacker who has previously intercepted or obtained a valid code. In addition, the 2FA system does not adequately restrict the number or frequency of login attempts. The OTP values are generated from a relatively small keyspace, making brute-force attacks more feasible. 

Exploitation Status: 

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 that Director be upgraded to one of the remediated software versions.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: Versa-Networks Versa Director.

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

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

## Is CVE-2025-23168 being exploited?

There is no known exploitation of CVE-2025-23168 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-2025-24288](https://insights.sbomify.com/CVE-2025-24288/): Hardcoded credentials in Director (critical 9.8)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23168 is a medium-severity vulnerability in Versa Director, published on 18 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23168 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-23168/ (Markdown: https://insights.sbomify.com/CVE-2025-23168/index.md)
```

## Sources

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

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