CVE-2021-21731
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 · uneditedA CSRF vulnerability exists in the management page of a ZTE product.The vulnerability is caused because the management page does not fully verify whether the request comes from a trusted user. The attacker could submit a malicious request to the affected device to delete the data. This affects: ZXCLOUD iRAI All versions up to KVM-ProductV6.03.04
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 · high confidenceA CSRF vulnerability in ZTE ZXCLOUD iRAI management interface fails to properly validate request origins, allowing attackers to craft malicious requests that execute actions (data deletion) on behalf of authenticated administrators through tricked browser requests.
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< 6.03.04CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 ZXCLOUD iRAI installationLocate the iRAI management interface (typically at /irai or /management paths) and confirm the product name in the web interface header or about pageAffected if The product is ZTE ZXCLOUD iRAI and the version displayed is below 6.03.04
-
Determine the installed software versionAccess the admin panel or check system information page within the iRAI management interface for the exact version numberAffected if The displayed version is less than 6.03.04 (e.g., 6.03.03, 6.02.x, etc.)
-
Verify management interface accessibilityConfirm the iRAI web interface is reachable over network (check if ports 443, 8080, or typical web service ports are open and responding)Affected if The management interface is externally accessible or accessible from untrusted networks
-
Inspect form submissions for anti-CSRF tokensUse browser developer tools or capture an HTTP request when submitting a state-changing form (such as data deletion or configuration change) and examine if a unique token parameter is present in the requestAffected if State-changing forms submit requests without any anti-CSRF token parameter or the token value remains static across sessions
-
Check HTTP header validationCapture HTTP requests to the iRAI interface and observe if Origin or Referer headers are validated server-side by testing with manipulated Origin header valuesAffected if The server accepts requests with arbitrary or missing Origin/Referer headers without rejecting them
You are affected if ZTE ZXCLOUD iRAI version is below 6.03.04 AND the management interface is accessible to potential attackers AND state-changing requests lack anti-CSRF token validation.
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 data6.03.04
Implement synchronizer token pattern with unique anti-CSRF tokens on all state-changing forms and validate Origin/Referer headers server-side; enforce SameSite cookie attributes.
- Consultation4.0 h
- Implementation16.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21731 — 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-2021-21731 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