CVE-2023-25651
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 SQL injection vulnerability in some ZTE mobile internet products. Due to insufficient input validation of SMS interface parameter, an authenticated attacker could use the vulnerability to execute SQL injection and cause information leak.
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 confidenceSQL injection vulnerability in ZTE mobile internet products stemming from insufficient input validation on SMS interface parameters. An authenticated attacker can inject malicious SQL queries through these parameters to extract sensitive information from the database.
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= bd_mf833u1v1.0.0b01= cr_lvwrgbmf286rv1.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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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.
-
Identify the ZTE device modelAccess the device web interface or check the device label to confirm the model number is MF833U1 or MF286RAffected if The device model is not MF833U1 or MF286R, then it is not affected by this specific CVE
-
Check the installed firmware versionLog into the device administration panel and navigate to the firmware or status page to view the current firmware version. Compare this against the affected versions: bd_mf833u1v1.0.0b01 for MF833U1 or cr_lvwrgbmf286rv1.0.0b04 for MF286RAffected if The installed firmware exactly matches one of the affected versions listed in the CVE, indicating the device may be vulnerable
-
Determine if SMS interface is accessibleCheck if the SMS messaging feature is enabled on the device. This can typically be found in the device settings under SMS or messaging configuration, or by attempting to access the SMS-related web endpoints if knownAffected if The SMS interface is disabled or not present, the SQL injection cannot be exploited through this vector
-
Verify authentication status for SMS featuresConfirm whether default credentials have been changed and whether remote management or SMS API endpoints are accessible without additional authentication barriersAffected if The device requires valid authentication credentials to access SMS functionality, the attacker would need valid credentials to exploit this SQL injection
A device is affected if it is a ZTE MF833U1 or MF286R model running the exact firmware versions bd_mf833u1v1.0.0b01 or cr_lvwrgbmf286rv1.0.0b04 respectively, with the SMS interface enabled and accessible to an authenticated attacker.
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 dataImplement proper input validation and use parameterized queries (prepared statements) for all SMS interface parameters. Additionally, apply least-privilege principles to database accounts used by the SMS interface to limit potential information exposure.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25651 — 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-2023-25651 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