CVE-2022-39074: There is an unauthorized access vulnerability in some ZTE mobile phones.
Noroxi assessment
Priority: Monitor (action score 13/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
There is an unauthorized access vulnerability in some ZTE mobile phones. If a malicious application is installed on the phone, it could start a non-public interface of an application without user permission.
- Published
- May 30, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 21th percentile
- CWE
- —
Report tools
Action score
13
Monitor
Low priority for now.
- CVSS
- 13 / 40 · 3.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| zte | blade a52 firmware | cpe:2.3:o:zte:blade_a52_firmware |
| zte | blade a52 | cpe:2.3:h:zte:blade_a52 |
| zte | blade a51 firmware | cpe:2.3:o:zte:blade_a51_firmware |
| zte | blade a51 | cpe:2.3:h:zte:blade_a51 |
| zte | blade a3 lite firmware | cpe:2.3:o:zte:blade_a3_lite_firmware |
| zte | blade a3 lite | cpe:2.3:h:zte:blade_a3_lite |
| zte | blade a5 2020 firmware | cpe:2.3:o:zte:blade_a5_2020_firmware |
| zte | blade a5 2020 | cpe:2.3:h:zte:blade_a5_2020 |
| zte | blade l210 firmware | cpe:2.3:o:zte:blade_l210_firmware |
| zte | blade l210 | cpe:2.3:h:zte:blade_l210 |
| zte | blade a7s firmware | cpe:2.3:o:zte:blade_a7s_firmware |
| zte | blade a7s | cpe:2.3:h:zte:blade_a7s |
and 22 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zte axon 40 ultra firmwarebefore 1.0.0b26
- zte blade a3 lite firmwarebefore m09
- zte blade a31 firmwarebefore m03
- zte blade a31 plus firmwarebefore m04
- zte blade a5 2019 firmwarebefore m13
- zte blade a5 2020 firmwarebefore m05
- zte blade a51 firmwarebefore m07
- zte blade a52 firmwarebefore m02
- zte blade a71 firmwarebefore 2.4
- zte blade a72 firmwarebefore 11.0.3
- zte blade a7s firmwarebefore 2.2
- zte blade l210 firmwarebefore 1.14
- zte blade v20 smart firmwarebefore 1.14
- zte blade v30 firmwarebefore 1.11
- zte blade v30 vita firmwarebefore 1.11
- zte blade v40 vita firmwarebefore 11.0.2_8045
- zte v40 pro firmwarebefore 11.0.4_9046
Versions reported by the vendor
Affected version ranges reported by the assigning authority (zte). Independent of NVD's CPE analysis and usually ahead of it.
n/a ZTE Blade A52, ZTE Blade A51, ZTE Blade A3 Lite, ZTE Blade A5 2020, ZTE Blade L210, ZTE Blade A7s, ZTE Blade A31, ZTE Blade A31 Plus, ZTE Blade A5 (2019), ZTE Blade A71, ZTE Blade A72, ZTE Blade V20 S
- All versions up to Z6356T_M01, All versions up to Blade A51_M06, All versions up to Blade A30_M08, All versions up to Blade A5 2020-T_M04, All versions up to GEN_MY_L210_V1.13, All versions up to CLA_affected
Same product
zte: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-39075There is an unauthorized access vulnerability in some ZTE mobile phones.28Monitor
- CVE-2022-39071There is an unauthorized access vulnerability in some ZTE mobile phones.28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0305 · May 31, 2023(ZTE Güvenlik Zafiyeti)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.