CVE-2025-66315
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 · uneditedThere is a configuration defect vulnerability in the version server of ZTE MF258K Pro products. Due to improper directory permission settings, an attacker can execute write permissions in a specific directory.
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 · moderate confidenceImproper directory permission settings in the version server of ZTE MF258K Pro products allow an attacker to execute write permissions in a specific directory, potentially enabling remote code execution or configuration tampering.
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= zte_mf258kpro_play_v1.0.0b03= zte_mf258pro_std_v1.0.0b04CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device modelAccess the device admin interface or check device labeling to verify the model is ZTE MF258K ProAffected if Device model is not ZTE MF258K Pro - unaffected
-
Identify firmware versionNavigate to device settings, status page, or use CLI command such as 'AT+CGMR' or 'AT+ZVERSION' to retrieve the firmware versionAffected if Firmware version does not match zte_mf258kpro_play_v1.0.0b03 or zte_mf258pro_std_v1.0.0b04 - unaffected
-
Locate affected directoryReview device configuration files or documentation for the directory referenced in version file management, or check web server document root for write-accessible directoriesAffected if Unable to identify the specific directory subject to the permission defect - manual investigation required
-
Check directory write permissionsUse file system commands (ls -ld or dir) on the identified directory to inspect permissions; look for world-writable (o+w) or group-writable permissions that should not be presentAffected if Directory shows overly permissive write access for unauthorized users or groups - likely affected
Device is affected if it is a ZTE MF258K Pro running firmware version zte_mf258kpro_play_v1.0.0b03 or zte_mf258pro_std_v1.0.0b04 AND the relevant directory has excessive write permissions.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict write permissions on the affected directory to authorized administrators only and ensure the directory does not allow execution of uploaded content.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66315 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-66315 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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