# CVE-2021-32454: SITEL CAP/PRX hardcoded credentials

> Hardcoded credentials in SITEL CAP/PRX firmware allow attackers to modify access, potentially locking out administrators.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7jp2-r62f-6m58

## What is CVE-2021-32454?

CVE-2021-32454 is a critical vulnerability in SITEL CAP/PRX, published on 17 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SITEL CAP/PRX firmware version 5.2.01 makes use of a hardcoded password. An attacker with access to the device could modify these credentials, leaving the administrators of the device without access.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Sitel-Sa Remote Cap\/Prx Firmware.

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

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

## Is CVE-2021-32454 being exploited?

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

## Other vulnerabilities in SITEL CAP/PRX

- [CVE-2021-32456](https://insights.sbomify.com/CVE-2021-32456/): SITEL CAP/PRX cleartext transmission of sensitive information (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-32454 is a critical vulnerability in SITEL CAP/PRX, published on 17 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-32454 in the wild and no public exploit code.

Affected product: SITEL CAP/PRX. 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-32454/ (Markdown: https://insights.sbomify.com/CVE-2021-32454/index.md)
```

## Sources

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

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