CVE-2025-24291VulnerabilityPublished 18 Jun 2025Updated 23 Jun 2025

CVE-2025-24291: Versa Director · Injection

Affects Versa DirectorSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.1Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 18 Jun 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 2026-10-26.

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 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
Versa Director	Affected =21.2.2 =21.2.3 =22.1.1 =22.1.2 =22.1.3 =22.1.4	Fixed in–

AI-suggested

1. Immediate upgrade: Organizations should prioritize upgrading Versa Director to the latest remediated versions provided by Versa Networks to eliminate the vulnerability. 2. Access control tightening: Restrict access to the Versa Director GUI strictly to trusted administrators and enforce multi-factor authentication to reduce the risk of compromised credentials. 3. Monitoring and logging: Implement enhanced monitoring of file upload activities and audit logs within Versa Director to detect anomalous or unauthorized file uploads promptly. 4. Network segmentation: Isolate the management network segment hosting Versa Director from general user networks to limit exposure and reduce the risk of lateral movement by attackers. 5. Incident response readiness: Prepare and test incident response plans specifically for potential misuse of the file upload functionality, including forensic analysis of uploaded files and system integrity checks. 6. User training: Educate administrators on the risks associated with file uploads and the importance of verifying file types and sources, even within trusted environments. 7. Application whitelisting: Where possible, implement application whitelisting or endpoint protection on the servers hosting Versa Director to prevent execution of unauthorized files placed on disk.

Description

The Versa Director SD-WAN orchestration platform provides functionality to upload various types of files. However, the Java code handling file uploads contains an argument injection vulnerability. By appending additional arguments to the file name, an attacker can bypass MIME type validation, allowing the upload of arbitrary file types. This flaw can be exploited to place a malicious file on disk. 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. There are no workarounds to disable the GUI option. Versa recommends that Director be upgraded to one of the remediated software versions.

Impact

For European organizations using Versa Director for SD-WAN orchestration, this vulnerability poses a moderate risk primarily to the confidentiality and integrity of their network management infrastructure. An attacker with authenticated access could upload malicious files that might be used to escalate privileges, implant backdoors, or exfiltrate sensitive configuration data. Given that SD-WAN controllers manage critical network traffic and policies, compromise could lead to unauthorized network manipulation or interception of data flows. Although availability is not directly impacted, the integrity breach could disrupt network security postures and trust in the orchestration platform. The requirement for high privileges and user interaction limits the attack surface to insiders or compromised accounts, but the potential for lateral movement and persistence within the network is significant. European organizations in sectors with stringent data protection regulations (e.g., finance, healthcare, critical infrastructure) could face compliance risks and reputational damage if this vulnerability is exploited. Additionally, the lack of workarounds means that remediation depends solely on timely patching, which may be challenging in complex operational environments.

CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements
Programming languages and supporting technologies might be chosen which are not subject to these issues.
Implementation
Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Server Side Include (SSI) Injection (opens in a new tab)
HTTP Request Splitting (opens in a new tab)
Command Line Execution through SQL Injection (opens in a new tab)
Double Encoding (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 19 Jun 2025, 00:03 UTC

WeaknessesCWE-74

Technical details

References

Community reviews

Related threats