CVE-2025-66315VulnerabilityPublished 9 Jan 2026

CVE-2025-66315: ZTE MF258K · Improper Privilege Management

Affects ZTE MF258KSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ZTEMF258K	Affected =ZTE_MF258kPRO_PLAY_V1.0.0B03 =ZTE_MF258PRO_STD_V1.0.0B04	Fixed in–

AI-suggested

1. Restrict network access to the version server and management interfaces of the ZTE MF258K Pro devices using firewall rules or network segmentation to limit exposure to trusted hosts only. 2. Monitor device logs and file system changes for unauthorized write activities in the affected directories to detect potential exploitation attempts early. 3. Apply principle of least privilege by ensuring that user accounts and services interacting with the device have minimal permissions necessary. 4. Engage with ZTE support or vendors to obtain firmware updates or patches addressing this vulnerability as soon as they become available. 5. If patching is not immediately possible, consider deploying network intrusion detection/prevention systems (IDS/IPS) with signatures targeting anomalous write operations or suspicious traffic patterns related to the version server. 6. Conduct regular security audits and vulnerability assessments on deployed ZTE devices to identify and remediate configuration weaknesses. 7. Educate network administrators about this vulnerability and enforce strict change management policies to prevent unauthorized configuration changes.

Description

CVE-2025-66315 is a medium severity vulnerability affecting ZTE MF258K Pro devices due to improper directory permission settings in the version server. This misconfiguration allows an attacker with limited privileges to write to a specific directory remotely without user interaction, potentially leading to denial of service or disruption of device functionality. The vulnerability does not impact confidentiality or integrity directly but affects availability. No known exploits are reported in the wild yet. The affected versions are ZTE_MF258kPRO_PLAY_V1.0.0B03 and ZTE_MF258PRO_STD_V1.0.0B04. Exploitation requires network access and limited privileges but no user interaction.

Impact

For European organizations, the primary impact of CVE-2025-66315 is on the availability of ZTE MF258K Pro devices, which may be used in telecom networks, IoT deployments, or enterprise connectivity solutions. Successful exploitation could lead to denial of service or operational disruptions, affecting network reliability and service continuity. While confidentiality and integrity are not directly compromised, availability issues can cascade into broader operational challenges, especially in critical infrastructure or service provider environments. The vulnerability could be exploited by internal threat actors or remote attackers with limited privileges, increasing the risk in multi-tenant or shared network environments. Disruptions could affect customer services, regulatory compliance, and operational costs. The absence of known exploits reduces immediate risk but does not eliminate the potential for future attacks, especially as the vulnerability becomes more widely known. Organizations relying on ZTE MF258K Pro devices should assess their exposure and implement compensating controls to minimize risk.

CWE-269Improper Privilege Management (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
Architecture and Design · Separation of Privilege
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Restful Privilege Elevation (opens in a new tab)
Privilege Abuse (opens in a new tab)
Privilege Escalation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.zte.com.cn/zte-iccp-isupport-webui/bulletin/detail/4891644183717871638 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Jan 2026, 10:10 UTC

WeaknessesCWE-269

Technical details

References

Community reviews

Related threats