# CVE-2021-22703: Information disclosure in PowerLogic ION7400, ION7650, ION83xx/84xx/85xx/8600, ION8650, ION8800, ION9000 and PM800 (see notification for affected versions)

> Attackers can intercept HTTP traffic to disclose user credentials on PowerLogic ION devices due to cleartext transmission.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2021
- **Updated:** 29 May 2026
- **Also known as:** GHSA-q772-ppcv-m7pf

## What is CVE-2021-22703?

CVE-2021-22703 is a medium-severity vulnerability in PowerLogic ION7400, ION7650, ION83xx/84xx/85xx/8600, ION8650, ION8800, ION9000 and PM800 (see notification for affected versions), published on 19 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A CWE-319: Cleartext transmission of sensitive information vulnerability exists in PowerLogic ION7400, ION7650, ION83xx/84xx/85xx/8600, ION8650, ION8800, ION9000 and PM800 (see notification for affected versions), that could cause disclosure of user credentials when a malicious actor intercepts HTTP network traffic between a user and the device.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 10 products.


Products: Schneider-Electric Powerlogic Ion7400 Firmware, Schneider-Electric Powerlogic Ion7650 Firmware, Schneider-Electric Powerlogic Ion8300 Firmware, Schneider-Electric Powerlogic Ion8400 Firmware, Schneider-Electric Powerlogic Ion8500 Firmware, Schneider-Electric Powerlogic Ion8600 Firmware, Schneider-Electric Powerlogic Ion8650 Firmware, Schneider-Electric Powerlogic Ion8800 Firmware, Schneider-Electric Powerlogic Ion9000 Firmware, Schneider-Electric Powerlogic Pm8000 Firmware.

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

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

## Is CVE-2021-22703 being exploited?

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

## Other vulnerabilities in PowerLogic ION7400, ION7650, ION83xx/84xx/85xx/8600, ION8650, ION8800, ION9000 and PM800 (see notification for affected versions)

- [CVE-2021-22714](https://insights.sbomify.com/CVE-2021-22714/): Memory corruption in PowerLogic ION7400, PM8000 and ION9000 (All versions prior to V3.0.0) (critical 9.8)
- [CVE-2022-46680](https://insights.sbomify.com/CVE-2022-46680/): Information disclosure in PowerLogic PM8000 (high 8.8)
- [CVE-2021-22701](https://insights.sbomify.com/CVE-2021-22701/): Cross-site request forgery in PowerLogic ION7400, ION7650, ION83xx/84xx/85xx/8600, ION8650, ION8800, ION9000 and PM800 (see notification for affected versions) (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22703 is a medium-severity vulnerability in PowerLogic ION7400, ION7650, ION83xx/84xx/85xx/8600, ION8650, ION8800, ION9000 and PM800 (see notification for affected versions), published on 19 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22703 in the wild and no public exploit code.

Affected product: PowerLogic ION7400, ION7650, ION83xx/84xx/85xx/8600, ION8650, ION8800, ION9000 and PM800 (see notification for affected versions). 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-22703/ (Markdown: https://insights.sbomify.com/CVE-2021-22703/index.md)
```

## Sources

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

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