External risk intelligence

Iskra iHUB Lite Unauthenticated Web Interface Access

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2025-13510

The vulnerability affects a smart metering gateway, which is a device designed for remote management and connectivity. Because the affected component is a web management interface that does not require authentication, it is inherently exposed as an internet-facing or network-accessible management service by design in common deployment scenarios.

Missing Authentication

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

The Iskra iHUB and iHUB Lite smart metering gateways have a critical vulnerability where their web management interface can be accessed and modified without any login, potentially allowing unauthorized users to alter essential device settings.

Unauthenticated access to device settings.
Protects critical infrastructure management.
Confirm relevance and exposure for smart meters.

Attack Path

How an attacker could exploit the issue

An attacker could target this smart metering gateway by accessing its web management interface from the network. Since no authentication is required, they can directly interact with the interface to alter critical device settings. This could lead to significant disruption of the device's intended operations.

Unauthenticated network access to the interface.
Modifying critical device settings.
Disruption of device operations.

Live Threat

Current exploitation, exposure, and threat context

Unauthenticated access to the web management interface of Iskra smart metering gateways could allow unauthorized users to view or alter critical device settings. This could impact the integrity and availability of metering services.

Device settings and operational integrity.
Via an unauthenticated web interface.
Disruption of metering services.

Operational Fix

Recommended remediation, mitigation, and detection steps

Identifying and prioritizing remediation for this vulnerability requires coordination between the asset owners responsible for the Iskra iHUB and iHUB Lite smart metering gateways, and the network or security teams monitoring external exposure. The first step is to inventory all instances of these gateways, confirm their network accessibility, and determine their business criticality. Once identified, the accountable owner should be found to plan and execute remediation activities, potentially involving vendor coordination.

Gateway owners should lead remediation efforts.
Verify external network exposure and criticality.
Plan vendor-assisted firmware updates.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the Iskra iHUB and iHUB Lite?

These are smart metering gateways used in utility networks. They act as communication bridges, collecting data from smart meters and managing device connectivity to support the operational requirements of energy and utility infrastructure systems.

What does CWE-306 mean for CVE-2025-13510?

This vulnerability is classified as CWE-306, which refers to 'Missing Authentication for Critical Function.' In the context of this CVE, it means the web management interface lacks the necessary security checks to verify who is accessing it, allowing any user to interact with the device as if they were a legitimate administrator.

How does an attacker trigger this vulnerability?

An attacker can trigger this by simply navigating to the web management interface over a network connection. No special conditions, secondary actions, or prior knowledge are required; the interface is designed to accept requests without asking for any login credentials or proof of identity.

Is my device at risk based on Halo Surface Signal?

According to Halo Surface Signal, there is a very high likelihood of risk because these gateways are intended for remote management and connectivity. Because the interface is reachable via the network by design, it is frequently exposed to external or wide-area network access, increasing the potential for unauthorized discovery.

What should I do first to manage this CVE?

Start by identifying every Iskra iHUB unit within your environment to establish a clear inventory. Once you have a list, verify which gateways are reachable over your network and coordinate with the asset owners to prioritize these devices for vendor-led firmware updates.

References

www.cisa.gov/news-events/ics-advisories/icsa-25-336-02

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.