CVE-2022-39072
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 validation of the input parameters of the SNTP interface, an authenticated attacker could use the vulnerability to execute stored XSS attacks.
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 the SNTP (Simple Network Time Protocol) interface of ZTE Mobile Internet products due to insufficient input parameter validation. An authenticated attacker can exploit this to inject malicious scripts, leading to stored XSS attacks against other users viewing the compromised data.
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= nordic_mf286r_b06= cr_tmoczmf289dv1.0.0b07CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 device model and firmware versionAccess the device web management interface and navigate to the status or system information page to view the exact model number and firmware version. Alternatively, check the device label or use AT commands via serial/telnet if available.Affected if The firmware version matches 'nordic_mf286r_b06' for MF286R or 'cr_tmoczmf289dv1.0.0b07' for MF289D
-
Locate SNTP configuration interfaceLog into the device web management panel and search for SNTP, NTP, or Time Settings under the network or system configuration sections.Affected if SNTP settings are present and accessible in the web interface
-
Verify SNTP functionality is enabledCheck the SNTP configuration page to determine if the SNTP client or server feature is currently enabled or configured with any server entries.Affected if SNTP is enabled or has server configurations saved
-
Confirm web interface accessibilityAttempt to access the device web management interface over HTTP/HTTPS to verify it is reachable on the local network.Affected if The web interface is accessible and accepts authentication credentials
A user is affected if they are running one of the specific firmware versions (nordic_mf286r_b06 or cr_tmoczmf289dv1.0.0b07) on the MF286R or MF289D devices respectively, and the SNTP feature is accessible through the device web management interface.
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 strict input validation and parameterized queries on the SNTP interface to prevent SQL injection. Additionally, apply output encoding when rendering any SNTP-related data to prevent stored XSS.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39072 — 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-2022-39072 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