CVE-2025-40598
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 · uneditedA Reflected cross-site scripting (XSS) vulnerability exists in the SMA100 series web interface, allowing a remote unauthenticated attacker to potentially execute arbitrary JavaScript code.
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 · moderate confidenceA reflected cross-site scripting (XSS) vulnerability exists in the SMA100 series web interface. The flaw allows a remote unauthenticated attacker to inject malicious JavaScript code through unsanitized user input that gets reflected in the HTTP response, potentially leading to session hijacking or credential theft.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SMA device modelAccess the device management interface or check the physical device label to confirm whether it is a Sonicwall SMA 210, SMA 410, or SMA 500v appliance.Affected if The device is not one of these three models.
-
Determine the installed firmware versionLog into the SMA web interface and navigate to System > Status or use the CLI command 'fwprint -v' to retrieve the current firmware version. Compare it against the fixed version 10.2.2.1-90sv.Affected if The firmware version is lower than 10.2.2.1-90sv.
-
Verify web interface accessibilityConfirm that the SMA web interface (typically HTTPS on port 443) is reachable from network locations where unauthenticated users could submit HTTP requests.Affected if The web interface is exposed to untrusted networks without additional filtering.
-
Test for reflected input in HTTP responsesSend a crafted HTTP GET request with a unique test string (such as 'XSStest123') in common query parameters (e.g., ?url=, ?redirect=, ?msg=) and inspect the response body to see if the string is reflected verbatim without encoding or sanitization.Affected if The test string appears in the response without HTML encoding (e.g., appears as <script> tags or unescaped special characters).
The environment is affected if the device is an SMA 210, 410, or 500v running firmware versions below 10.2.2.1-90sv and the web interface is accessible to potential attackers.
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
Apply vendor-supplied patches for CVE-2025-40598; in the interim, implement web application firewall (WAF) rules to block XSS payloads in HTTP requests.
SMA 100 series firmware 10.2.2.1-90sv or later
- Backup the current device configuration before proceeding with firmware upgrade
- Download the firmware version 10.2.2.1-90sv (or newer) from the official SonicWall support portal at my.sonicwall.com
- Access the SMA100 device web management interface
- Navigate to System Administration > Firmware Management
- Upload and install the firmware version 10.2.2.1-90sv or newer
- After installation, verify the device is running the updated firmware version
- Confirm the web interface is accessible and functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40598 — 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-40598 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