What is CVE-2019-7481?

CVE-2019-7481 is SonicWall SMA100 SQL Injection Vulnerability. The supplied enrichment data classifies it as Injection mapped to CWE-89 SQL Injection.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Yes. The supplied enrichment data lists CVE-2019-7481 in CISA KEV with required action: Apply updates per vendor instructions.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

12 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, database audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2019-7481 using CVSS 7.5, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: TeamTNT (), Kinsing (), Cron (), Ransomware use: Known. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVRansomwarehighInjectionpublic exploit

CVE-2019-7481

CVE-2019-7481 — SonicWall SMA100 SQL Injection Vulnerability

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.

Published Dec 17, 2019Updated Aug 12, 2026Sources: NVD, SonicWall (CNA), CISA, FIRST EPSS, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Nov 3, 2021

EPSS

100%

top of FIRST's scoreset

Affects

SonicWall

SMA100

CVSS base

7.5

high · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade SMA100 to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply updates per vendor instructions.

Federal deadline May 3, 2022 — passed 1,595 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
SonicWall	SMA100	9.0.0.3 and earlier	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

High

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.5	CVSS 3.1	high	3.9	3.6	NVD, CNA
5	CVSS 2.0	medium	10	2.9	NVD

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Read Application Data
Bypass Protection Mechanism
Modify Application Data

Mitigation: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.

Weakness & attack patterns

CWE-89SQL Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-470 · Expanding Control over the Operating System from the DatabaseCAPEC-7 · Blind SQL InjectionCAPEC-109 · Object Relational Mapping InjectionCAPEC-110 · SQL Injection through SOAP Parameter TamperingCAPEC-108 · Command Line Execution through SQL InjectionCAPEC-66 · SQL Injection

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Nov 3, 2021

Federal deadline

May 3, 2022

passed 1,595 days ago

Ransomware use

Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable SMA100.
Monitor for scanner or exploit-pattern traffic after 12 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSdatabase audit logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

TeamTNTKinsingCron

hostnameenrollmentdm.com73
Maltrail Malware Feeds · Jan 11, 2025

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.5 (AV:N)
Aug 12, 2026 · NVD
2025
Bulletin released on NIST.
Oct 16, 2025 · SOCRadar CTI
Bulletin released on NIST.
Oct 16, 2025 · SOCRadar CTI
Bulletin released on NIST.
Feb 7, 2025 · SOCRadar CTI
2023
CVE is exploited. "Ostorlab/KEV"
Dec 26, 2023 · SOCRadar CTI
CVE is exploited. "Ostorlab/known_exploited_vulnerbilities_detectors"
Dec 10, 2023 · SOCRadar CTI
CVE is exploited. "SonicWall SMA100 SQL Injection Vulnerability"
May 26, 2023 · SOCRadar CTI
2021
Added to CISA KEV catalog
Nov 3, 2021 · CISA
CVE is exploited. "SonicWall SMA100 9.0.0.3 and Earlier SQL Injection"
Nov 3, 2021 · SOCRadar CTI
2020
Bulletin released on MITRE_REFERENCES.
Sep 16, 2020 · SOCRadar CTI
2019
Initial · CVE published
Dec 17, 2019 · NVD
CVE published by NIST.
Dec 17, 2019 · SOCRadar CTI

Source activity

Readings a source repeats on a schedule, counted rather than listed.

11×Github ReposFeb 26, 2020 – Jan 23, 2024 · SOCRadar CTI
4×ModifiedDec 17, 2019 – Mar 14, 2025 · SOCRadar CTI

References

3 on the record

psirt.global.sonicwall.com/vuln-detail/SNWLID-2019-0016
Vendor Advisory, NIST, MITRE_REFERENCES
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-7481
US Government Resource, NIST
nvd.nist.gov/vuln/detail/CVE-2019-7481
Vendor Advisory

Coverage

4 stories from the feeds we poll

Elsewhere on this site

SonicWallevery CVE for this vendor
November 2021what else CISA listed
Injectionsame class
CWE-89other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 1 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2019-7481 is SonicWall SMA100 SQL Injection Vulnerability, a high vulnerability affecting SMA100 from SonicWall. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 12 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.5 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.