Skip to content
IoT

CVE-2019-25291

9.3
Critical
EPSS 0.42%Jan 8, 2026

Hard-coded credentials in INIM SmartLiving <=6.x allow persistent access.

common questions

Is CVE-2019-25291 being exploited?

Not confirmed. CVE-2019-25291 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.

How severe is CVE-2019-25291?

CVE-2019-25291 is rated Critical with a CVSS score of 9.3. 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-25291?

Not known from our data. No patch reference has been recorded for CVE-2019-25291, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2019-25291 affect?

CVE-2019-25291 affects INIM SmartLiving SmartLAN/SI <=6.x. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2019-25291?

Update firmware when available; rotate credentials; restrict remote access.

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

executive summary
technical analysis
affected
INIM SmartLiving SmartLAN/SI <=6.x
impact

Unauthorized login with hard-coded creds grants full control of affected devices.

action required

Immediate action required

affected versions
INIM Electronics s.r.l. Smartliving SmartLAN/G/SI
  • affected<= 6.0
  • affected505
  • affected515
  • affected1050
  • affected1050/G3
  • affected10100L
  • affected10100L/G3

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free