dbcve.org
Sma6210 FirmwareOperating system · Sonicwall

CVE-2026-4112

HIGH · 7.2 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 12.4.3-03387 / 12.5.0-02624 or later.
See remediation →
78/100
Remediation priority · High
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
Improper neutralization of special elements used in an SQL command (“SQL Injection”) in SonicWall SMA1000 series appliances allows a remote authenticated attacker with read-only administrator privileges to escalate privileges to primary administrator.

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

SQL injection vulnerability in SonicWall SMA1000 series appliances allows authenticated read-only administrators to escalate privileges to primary administrator through improper neutralization of special elements in SQL commands.

MitigationApply vendor-supplied patch or firmware update for SMA1000 series; until patched, limit read-only administrator access to trusted personnel only and monitor for anomalous SQL queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sma6210 FirmwareOperating system
Affected:< 12.4.3-03387>= 12.5.0, < 12.5.0-02624
Sma6200 FirmwareOperating system
Affected:< 12.4.3-03387>= 12.5.0, < 12.5.0-02624
Sma7200 FirmwareOperating system
Affected:< 12.4.3-03387>= 12.5.0, < 12.5.0-02624
Sma7210 FirmwareOperating system
Affected:< 12.4.3-03387>= 12.5.0, < 12.5.0-02624
Sma8200vApplication
Affected:< 12.4.3-03387>= 12.5.0, < 12.5.0-02624

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 checks

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

  1. Identify the SMA100 appliance model
    Access the appliance administrative interface or check the device label/system information to confirm the exact model (Sma6210, Sma6200, Sma7200, Sma7210, or Sma8200v)
    Affected if Model is one of Sma6210, Sma6200, Sma7200, Sma7210, or Sma8200v
  2. Determine the installed firmware version
    Log into the SMA100 administrative console and navigate to System > Status or use the CLI command 'show version' to retrieve the current firmware build number
    Affected if Firmware version is less than 12.4.3-03387, OR firmware version is 12.5.0 or higher but less than 12.5.0-02624
  3. Verify the presence of read-only administrator accounts
    Access the appliance user management or administration settings and review the list of configured administrator accounts and their assigned roles
    Affected if One or more read-only administrator accounts are configured on the appliance

The environment is affected if the appliance is an SMA1000 series model (Sma6210, Sma6200, Sma7200, Sma7210, or Sma8200v) running firmware version < 12.4.3-03387 or >= 12.5.0 but < 12.5.0-02624, and read-only administrator accounts exist on the system.

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
Upgrade available Upgrade to 12.4.3-03387 / 12.5.0-02624 or later
Fixed in 12.4.3-0338712.5.0-02624
Interim mitigation

Apply vendor-supplied patch or firmware update for SMA1000 series; until patched, limit read-only administrator access to trusted personnel only and monitor for anomalous SQL queries.

Recommended fix High confidence

Upgrade to Sma6210/Sma6200/Sma7200/Sma7210/Sma8200v firmware version 12.4.3-03387 or later, OR version 12.5.0-02624 or later

  1. 1. Identify the current firmware version of the SonicWall SMA100 appliance by navigating to System > Status or using the CLI command 'sysinfo get version'
  2. 2. Determine which firmware branch is currently installed (12.4.x or 12.5.x)
  3. 3. Download the fixed firmware version from the SonicWall support portal: either version 12.4.3-03387 or later, or version 12.5.0-02624 or later
  4. 4. Back up the current appliance configuration from System > Settings > Backup/Restore
  5. 5. Upload the new firmware file from System > Firmware > Upload
  6. 6. After upload completes, proceed with the firmware installation and allow the appliance to reboot
  7. 7. Verify the new firmware version is installed by checking System > Status
  8. 8. Confirm the SQL injection vulnerability is remediated by logging in with a read-only administrator account and verifying privilege escalation is no longer possible
Caveat Review SonicWall release notes for any configuration or behavioral changes between versions before upgrading

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

Fix this in Sma6210 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4112 — 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-2026-4112 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