# CVE-2021-22825: Information disclosure in n/a

> An attacker can access sensitive information and gain elevated privileges if a privileged user clicks a malicious URL, compromising the security token.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Jan 2022
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-mfxr-wxm4-4j5r

## What is CVE-2021-22825?

CVE-2021-22825 is a high-severity vulnerability in n/a, published on 28 Jan 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A CWE-200: Exposure of Sensitive Information to an Unauthorized Actor vulnerability exists that could allow an attacker to access the system with elevated privileges when a privileged account clicks on a malicious URL that compromises the security token. Affected Products: AP7xxxx and AP8xxx with NMC2 (V6.9.6 or earlier), AP7xxx and AP8xxx with NMC3 (V1.1.0.3 or earlier), and APDU9xxx with NMC3 (V1.0.0.28 or earlier)

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: Schneider-Electric Rack Power Distribution Unit With Network Management Card 2 Firmware, Schneider-Electric Rack Power Distribution Unit With Network Management Card 3 Firmware.

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

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

## Is CVE-2021-22825 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22825 is a high-severity vulnerability in n/a, published on 28 Jan 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-22825 in the wild and no public exploit code.

Affected product: n/a. 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-22825/ (Markdown: https://insights.sbomify.com/CVE-2021-22825/index.md)
```

## Sources

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

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