CVE-2025-40599
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 · uneditedAn authenticated arbitrary file upload vulnerability exists in the SMA 100 series web management interface. A remote attacker with administrative privileges can exploit this flaw to upload arbitrary files to the system, potentially leading to remote code execution.
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 confidenceAn authenticated arbitrary file upload vulnerability in the SMA 100 series web management interface allows a remote attacker with administrative privileges to upload arbitrary files to the system, which can lead to remote code execution.
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< 10.2.2.1-90sv< 10.2.2.1-90sv< 10.2.2.1-90svCVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 SMA device modelLog into the SMA web management interface and check the System Status or Device Information page for the exact model number (SMA 210, SMA 410, or SMA 500v).Affected if The device model is one of SMA 210, SMA 410, or SMA 500v.
-
Check installed firmware versionNavigate to the System Administration or Firmware Update section in the web interface to view the current firmware version. Alternatively, access the device via SSH and run: 'version' or 'show version'.Affected if The firmware version is lower than 10.2.2.1-90sv.
-
Verify web management interface accessibilityConfirm the SMA web management interface (typically on port 443) is accessible from network locations. Check firewall rules or access lists that govern who can reach the management interface.Affected if The web management interface is accessible from untrusted networks.
-
Review administrative account statusCheck the Users or Administrators section in the web interface to confirm administrative accounts exist. Note any unexpected or unauthorized admin accounts.Affected if Administrative credentials are known or accessible to untrusted users.
-
Inspect for suspicious uploaded filesCheck the following locations for unexpected files: /etc/httpd/html/ (web root), /tmp/, and any custom upload directories. Use SSH to list files: 'ls -la /etc/httpd/html/' and 'ls -la /tmp/'.Affected if Unexpected or unknown files are present in web-accessible directories or /tmp/.
The environment is affected if you are running an SMA 210, 410, or 500v with firmware version lower than 10.2.2.1-90sv and the web management interface is accessible with administrative credentials.
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.
dbcve · scoped10.2.2.1-90sv
Restrict administrative access to trusted networks using network segmentation, implement strict file type validation and content inspection on the web interface, and apply vendor-provided patches when available.
10.2.2.1-90sv
- Log into the SMA web management interface with administrative credentials
- Navigate to System > Firmware or Settings > Device > Firmware Upgrade
- Download the firmware version 10.2.2.1-90sv from the official SonicWall support portal (psirt.global.sonicwall.com)
- In the firmware upgrade interface, select the downloaded firmware file and initiate the upgrade
- Wait for the upgrade process to complete - do not power off the device during this process
- After the device reboots, verify the firmware version shows 10.2.2.1-90sv in the web interface
- As a security precaution, change the administrator password since the vulnerability required admin access
- Verify that the SMA services are functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40599 — 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-40599 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