Skip to content

CVE-2019-7481

Vulnerability in SonicWall SMA100 allow unauthenticated user to gain read-only access to unauthorized resources. This vulnerablity impacted SMA100 version 9.0.0.3 and earlier.

CVSS
7.5Highscored by CISA
Exploited in the wild
Yes, in CISA KEV since 3 Nov 2021CISA deadline for US federal agencies: 3 May 2022known use in ransomware campaigns
EPSS
99.9%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
17 Dec 2019analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Yes. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
SonicWall SMA1009.0.0.3 and earlierVendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • sonicwall:sma_100_firmware

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Yes. SQL injection puts SQL syntax into a request parameter, and WAF signatures recognise that syntax well.

Also consider: parameterized queries · ORM

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 3 Nov 2021. Known use in ransomware campaigns.
CISA due date
3 May 2022, the remediation deadline for US federal agencies
CISA required action
Apply updates per vendor instructions.
Public exploit code
Detection templates only, no public exploit found: 1 Nuclei template
CISA SSVC
exploitation active, automatable yes, technical impact partialAssessed by CISA 26 Oct 2021 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Nuclei

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 17 Dec 2019Published
  2. 26 Oct 2021CISA SSVC assessment: exploitation active678 days (about 2 years) later
  3. 3 Nov 2021Added to CISA KEV (exploited in the wild)8 days later
  4. 3 May 2022CISA remediation due date (US federal agencies)181 days (about 6 months) later
  5. 12 Aug 2026CVE record last updated1,562 days (about 4 years) later
  6. 12 Nov 2026Analysed by vulneraibility.com92 days (about 3 months) later

CVSS vector

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

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityNoneNo unauthorised modification.
AvailabilityNoneThe service stays up.

Common questions

Is CVE-2019-7481 being exploited?

Yes. CVE-2019-7481 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2019-7481?

CVE-2019-7481 is rated High with a CVSS score of 7.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2019-7481?

Yes. A fix has been recorded for CVE-2019-7481. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2019-7481 affect?

CVE-2019-7481 affects sonicwall:sma_100_firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

2 references in the CVE record, grouped by the tags the record gives them.

Other links (2)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com