Sonicwall sma100, OS command injection: 8 records, one defect family
Sonicwall sma100 has been reported 8 separate times for the same kind of mistake, CWE-78, between 2021-01-09 and 2025-05-07. A defect family is our own grouping of the CVE corpus: every record naming one product and one weakness class, collected so a repeat is visible as a repeat. No public source publishes this, and what this page counts is how often this one product has gone wrong in this one way.
What this page is, and what it is not
The records are public. This grouping is not. No source publishes defect families, so we built them: every record in the corpus sorted by the product an authority named and the weakness class carried with it, 21316 families over 105586 records. This one holds every record that names Sonicwall sma100 and carries CWE-78, matched character for character. We show the join because a grouping you cannot check is a grouping you should not cite.
One record is an incident. 8 filings, between 2021-01-09 and 2025-05-07, all landing on the same weakness class in the same product, is a habit in what gets reported here, and a habit is something you can plan around. This is what we held on 2026-09-20.
A repeat is evidence about where to look. If you are reviewing Sonicwall sma100, the records below say which mistake has already been found more than once, which is the cheapest place a reviewer can start. If you are asking the vendor a question, a count under one weakness class is a better question than any single record is.
What this page cannot tell you is decided by what was joined. A product name and a weakness class settled membership, so those two values are the whole of what the page asserts. Records here may sit in the same line of code or in unrelated parts of the product, and we hold no value that separates those cases. A fixed version named in one record closes that record and says nothing about the others. And nothing here describes anyone's systems, because no value in this family connects a product name to an installation.
The names the authorities used
One spelling, used by every authority that filed one of these records: sonicwall sma100.
Family membership: held values. Joined on the product and weakness class the assigning authorities wrote, with no model involved.
What the records offer
No record in this family publishes a fixed version in held sources.
2 records are listed by CISA with a required action, which carries a federal remediation deadline on its own page.
The earliest was published 2021-01-09 and the latest 2025-05-07. That span is how long this product kept producing this weakness, not how long any one record took to fix.
What this family was researched, not held
The SMA100 management interface kept running text as commands
Every record here has the same shape: input reaching the SMA100 management interface is executed as an operating system command, in most cases as the 'nobody' user and in most cases after the attacker has authenticated. Rapid7, which found five of the flaws SonicWall published on 7 December 2021, showed why the shape recurred: the filters scanned for the usual shell characters but not for a newline, and these appliances are designed to be exposed to the internet. The grading of the older records changed years later. In April 2025 SonicWall reclassified a 2021 record from denial of service to remote code execution and raised its score to 7.2, saying it was believed to be actively exploited; CISA added it to the known exploited catalog on 16 April 2025 with a federal deadline of 7 May 2025, and Arctic Wolf reported exploitation going back to at least January 2025. On 30 April 2025 SonicWall updated its advisory for the 2023 record to say it was potentially being exploited in the wild, with the fix in firmware 10.2.1.14-75sv and later.
The management interface is the surface every one of these lands on, and post-authentication is not out of reach when an administrator credential or session can be stolen. A record you closed on its original rating can be regraded years afterwards, so the old ones in this grouping are worth rechecking against the current advisory.
This grouping says these records read alike. It does not say they share a vulnerability or an estate, and applying the fix for one of them does not address another.
Written from rapid7.com, bleepingcomputer.com, bleepingcomputer.com. Stated at high confidence. Nothing in this box is a value the index holds, and none of it opens a receipt.
What this page does not cover
This is a family of records that read alike. It is not a shared vulnerability, not an inventory, and not a statement that one fix closes the rest. Each record's own state, its own dates and its own receipts are on its own page.
Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.
Everything this vendor has, including records outside this family:
8 records, read from the index as it stood on 20 Sep 2026. Every row opens the record it names, and every value on that record opens its own receipt.