CVE-2025-23172
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Versa Director SD-WAN orchestration platform includes a Webhook feature for sending notifications to external HTTP endpoints. However, the "Add Webhook" and "Test Webhook" functionalities can be abused by an authenticated user to send crafted HTTP requests to localhost. This can be leveraged to execute commands on behalf of the versa user, who has sudo privileges, potentially leading to privilege escalation or remote code execution. 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: There are no workarounds to disable the GUI option. Versa recommends that Director be upgraded to one of the remediated software versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe vulnerability exists in the Webhook feature of Versa Director SD-WAN platform, where authenticated users can abuse 'Add Webhook' and 'Test Webhook' functionalities to send crafted HTTP requests to localhost. Since the versa service user has sudo privileges, thisSSRF-like behavior can be leveraged for privilege escalation to execute arbitrary commands with elevated permissions, potentially achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Versa Director installationCheck system for Versa Director software components - look for /opt/versa directory or run 'rpm -qa | grep -i versa' to list installed Versa packagesAffected if Versa Director software is installed on the system
-
Verify Webhook feature configurationInspect Versa Director GUI or configuration files for webhook-related settings - check if Webhook feature has been configured or used by examining /opt/versairector/conf or similar configuration directoriesAffected if Webhook feature is enabled or has been configured in Versa Director
-
Check installed Versa Director versionRun 'rpm -q versa-director' or check the Versa Director GUI 'About' page to obtain the exact version numberAffected if Installed version falls within the affected range and has not been patched
-
Verify versa service user sudo privilegesCheck /etc/sudoers or run 'sudo -l -U versa' to list sudo privileges for the versa service accountAffected if The versa user has elevated sudo permissions that could enable command execution
-
Audit webhook test logs for suspicious activityReview Versa Director logs in /var/log/versa for Webhook Test execution records or HTTP requests to localhost/internal addressesAffected if Logs show webhook requests targeting localhost or internal network addresses from the Webhook feature
User is affected if Versa Director is running with the Webhook feature accessible and the installed version has not been upgraded to the remediated release, combined with the versa service account having sudo privileges.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Versa Director to the remediated software versions as specified by Versa Networks; no workaround exists to disable the vulnerable GUI feature.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23172 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23172 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data