dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-41233

MEDIUM · 6.8 CVSS v3.1 Published 2025-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Description: VMware AVI Load Balancer contains an authenticated blind SQL Injection vulnerability. VMware has evaluated the severity of the issue to be in the Moderate severity range https://www.broadcom.com/support/vmware-services/security-response  with a maximum CVSSv3 base score of 6.8 https://www.first.org/cvss/calculator/3-0#CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N . Known Attack Vectors: An authenticated malicious user with network access may be able to use specially crafted SQL queries to gain database access. Resolution: To remediate CVE-2025-41233 apply the patches to the Avi Controller listed in the 'Fixed Version' column of the 'Response Matrix' found below. Workarounds: None. Additional Documentation: None. Acknowledgements: VMware would like to thank Alexandru Copaceanu https://www.linkedin.com/in/alexandru-copaceanu-b39aaa1a8/  for reporting this issue to us. Notes: None.   Response Matrix: ProductVersionRunning OnCVECVSSv4SeverityFixed VersionWorkaroundsAdditional DocumentsVMware Avi Load Balancer30.1.1AnyCVE-2025-41233 6.8 https://www.first.org/cvss/calculator/3-0#CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N Moderate 30.1.2-2p3 https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/30-1/vmware-avi-load-balancer-release-notes/release-notes-30-1-2.html NoneNoneVMware Avi Load Balancer30.1.2AnyCVE-2025-41233 6.8 https://www.first.org/cvss/calculator/3-0#CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N Moderate 30.1.2-2p3 https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/30-1/vmware-avi-load-balancer-release-notes/release-notes-30-1-2.html NoneNoneVMware Avi Load Balancer30.2.1AnyCVE-2025-41233 6.8 https://www.first.org/cvss/calculator/3-0#CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N Moderate 30.2.1-2p6 https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/30-2/vmware-avi-load-balancer-release-notes/release-notes-for-avi-load-balancer-version-30-2-1.html NoneNoneVMware Avi Load Balancer30.2.2AnyCVE-2025-41233 6.8 https://www.first.org/cvss/calculator/3-0#CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N Moderate 30.2.2-2p5 https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/30-2/vmware-avi-load-balancer-release-notes/release-notes-for-avi-load-balancer-version-30-2-2.html NoneNoneVMware Avi Load Balancer30.2.3AnyCVE-2025-41233N/AN/AUnaffectedNoneNoneVMware Avi Load Balancer31.1.1AnyCVE-2025-41233 6.8 https://www.first.org/cvss/calculator/3-0#CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N Moderate 31.1.1-2p2 https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/31-1/vmware-avi-load-balancer-release-notes/Release-Note-Section-20627.html NoneNone CWE-89 in the Avi Load Balancer component of VMware allows an authenticated attacker to execute blind SQL injections in versions 30.1.1, 30.1.2, 30.2.1, and 30.2.2 due to improper input validation, enabling unauthorized database access.

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 confidence

VMware AVI Load Balancer contains an authenticated blind SQL injection vulnerability (CWE-89) in versions 30.1.1, 30.1.2, 30.2.1, and 30.2.2 due to improper input validation. An authenticated attacker with high privileges and network access can execute specially crafted SQL queries to infer database information through blind injection techniques, achieving high confidentiality impact.

MitigationApply the vendor patches to upgrade to the fixed versions (30.1.2-2p3, 30.2.1-2p6, 30.2.2-2p5, or 31.1.1-2p2). No workarounds are available.

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
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify VMware AVI Load Balancer version
    Log into the AVI Load Balancer management interface and navigate to the Dashboard or Administration > System > Settings to view the installed software version. Alternatively, use the CLI command 'show version' if SSH access is available.
    Affected if The installed version is 30.1.1, 30.1.2, 30.2.1, or 30.2.2 exactly.
  2. Confirm version is in vulnerable range
    Compare the identified version number against the affected list (30.1.1, 30.1.2, 30.2.1, 30.2.2). If running a version between these (e.g., 30.1.1 to 30.1.2), treat as potentially affected unless explicitly patched.
    Affected if The version matches one of the four affected versions listed.
  3. Verify management interface accessibility
    Confirm the AVI Load Balancer management interface (typically ports 443 or 8080) is exposed to the network. Check firewall rules and access lists to determine if the interface is reachable from untrusted networks.
    Affected if The management interface is accessible from network segments accessible to untrusted users.
  4. Review high-privilege user accounts
    In the AVI management interface, navigate to Administration > User Management > Users to enumerate accounts with high privileges (Admin role). Since this is an authenticated vulnerability, such accounts are required for exploitation.
    Affected if High-privilege user accounts exist in the system.

A user is affected if they are running any of versions 30.1.1, 30.1.2, 30.2.1, or 30.2.2 of VMware AVI Load Balancer and have the management interface accessible with high-privilege accounts present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patches to upgrade to the fixed versions (30.1.2-2p3, 30.2.1-2p6, 30.2.2-2p5, or 31.1.1-2p2). No workarounds are available.

Recommended fix High confidence

Upgrade to the applicable patch version: 30.1.2-2p3 (for 30.1.1/30.1.2), 30.2.1-2p6 (for 30.2.1), 30.2.2-2p5 (for 30.2.2), or 31.1.1-2p2 (for 31.1.1)

  1. 1. Identify the current version of VMware Avi Load Balancer by logging into the Avi Controller CLI or UI and checking the version information.
  2. 2. Based on your current version, determine the required patch version: for 30.1.1 or 30.1.2 upgrade to 30.1.2-2p3; for 30.2.1 upgrade to 30.2.1-2p6; for 30.2.2 upgrade to 30.2.2-2p5; for 31.1.1 upgrade to 31.1.1-2p2.
  3. 3. Download the appropriate patch file from the Broadcom support portal (support.broadcom.com) or access the release notes links provided in the Response Matrix for patch details.
  4. 4. Back up the Avi Controller configuration before applying the patch.
  5. 5. Apply the patch to the Avi Controller following VMware's standard patch upgrade procedure - typically via the CLI 'patch upload' and 'patch apply' commands, or via the UI under Administration > Settings > Patch Management.
  6. 6. After patch installation completes, verify the patch was successfully applied by checking the Avi Controller version confirms the new patch level.
  7. 7. Validate that the SQL injection vulnerability is remediated by confirming the patch version is running.
Caveat Patch releases are typically low-risk updates; review release notes for any specific caveats before applying

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41233 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41233 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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