dbcve.org
Lares FirmwareOperating system · Kseniasecurity

CVE-2025-15113

CRITICAL · 9.3 CVSS v3.1 Published 2025-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
98/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
Ksenia Security lares (legacy model) Home Automation version 1.6 contains an unprotected endpoint vulnerability that allows authenticated attackers to upload MPFS File System binary images. Attackers can exploit this vulnerability to overwrite flash program memory and potentially execute arbitrary code on the home automation system's web server.

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 · high confidence

Ksenia Security lares legacy home automation system version 1.6 contains an unprotected endpoint that allows authenticated attackers to upload MPFS (Microchip PIC32 File System) binary images. Since MPFS images are written directly to flash memory, attackers can overwrite program memory and achieve arbitrary code execution on the device's web server.

MitigationImplement proper authentication and authorization controls on the MPFS upload endpoint, add file type validation, and restrict network access to the legacy device. Consider firmware update from vendor or device replacement if no patch is available.

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
Lares FirmwareOperating system
Affected:= 1.6

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device and firmware version
    Access the device's web interface or use SNMP/SSH to retrieve the system information. Look for the firmware version in the device status or about page. Alternatively, check the HTTP headers or the login page source for version indicators.
    Affected if The firmware version is exactly 1.6 (Lares Legacy system)
  2. Locate the MPFS upload endpoint
    Search the web application for endpoints related to firmware upload, MPFS, or image updates. Common paths include /upload, /firmware, /mpfs, /update, or similar. Check the HTML forms and JavaScript for any file upload functionality.
    Affected if An MPFS upload endpoint exists and is accessible on the device web server
  3. Verify authentication requirements on the upload endpoint
    Attempt to access the identified upload endpoint without logging in, or examine the endpoint's source code and server configuration to determine if authentication is enforced.
    Affected if The MPFS upload endpoint does not require valid authentication or allows unauthorized access
  4. Check for file type validation on upload functionality
    Inspect the upload form and server-side handling to determine if file type validation (e.g., checking MPFS magic bytes, file extension restrictions) is implemented before writing to flash.
    Affected if No file type or content validation is performed before MPFS image is written to flash memory
  5. Confirm network exposure of the legacy device
    Review network firewall rules, access control lists, and device network configuration to determine if the web interface is exposed to untrusted networks or the internet.
    Affected if The device web interface is accessible from untrusted network segments or the internet

You are affected if you are running Ksenia Security Lares firmware version 1.6 and the MPFS upload endpoint is accessible (with or without authentication) on your device.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization controls on the MPFS upload endpoint, add file type validation, and restrict network access to the legacy device. Consider firmware update from vendor or device replacement if no patch is available.

Fix this in Lares Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15113 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15113 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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