# CVE-2021-21751: Open redirect in ZXIN10 CMS

> High-privilege attackers can tamper with URLs in the ZTE BigVideo analysis product due to inconsistent validation, causing service exceptions.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-j27v-qfg5-c437

## What is CVE-2021-21751?

CVE-2021-21751 is a high-severity vulnerability in ZXIN10 CMS, published on 27 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ZTE BigVideo analysis product has an input verification vulnerability. Due to the inconsistency between the front and back verifications when configuring the large screen page, an attacker with high privileges could exploit this vulnerability to tamper with the URL and cause service exception.

## Which versions are affected by CVE-2021-21751?

It affects 1 product.


Products: Zte Zxin10 Cms.

## How do I fix CVE-2021-21751?

No fix has been published for CVE-2021-21751 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-21751 being exploited?

There is no known exploitation of CVE-2021-21751 in the wild and no public exploit code.

## Other vulnerabilities in ZXIN10 CMS

- [CVE-2021-21750](https://insights.sbomify.com/CVE-2021-21750/): Privilege escalation in ZXIN10 CMS (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-21751 and fix it if it is affected.

What it is: CVE-2021-21751 is a high-severity vulnerability in ZXIN10 CMS, published on 27 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-21751 in the wild and no public exploit code.

Affected product: ZXIN10 CMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-21751/ (Markdown: https://insights.sbomify.com/CVE-2021-21751/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-21751
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-21751
- OSV: https://osv.dev/vulnerability/CVE-2021-21751

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-21751/
Summaries are generated and may contain mistakes; the official description above is the record.