cve.bz

CVE-2026-49001 zte zxunipos nds-lte: Cross Site Reference Forgery

5.3 mediumEPSS 0.1%

Medium (5.3) in zte zxunipos nds-lte. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
Cross-site request forgery (CSRF) vulnerabilities allow attackers to exploit a user's authenticated session to forge cross-site requests, inducing the execution of unintended operations such as tampering with configuration data.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:H/A:L
EPSS
0.1% (unchanged from 0.1% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-49001 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-49001?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-49001?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-49001 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-49001

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-49001](https://cve.bz/cve/badge/CVE-2026-49001.svg)](https://cve.bz/cve/CVE-2026-49001)

HTML:

<a href="https://cve.bz/cve/CVE-2026-49001"><img src="https://cve.bz/cve/badge/CVE-2026-49001.svg" alt="CVE-2026-49001"></a>

Affected

  • zte:zxunipos nds-lte

Versions

From the CNA's record in the CVE List.

ProductAffected
ZTE ZXUniPOS NDS-LTEVersions < V24.40.40CP01 (excluding V24.30.40CP03, V24.40.40CP01

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON