# 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)

> Cross-site request forgery in PowerLogic ION devices allows attackers to force users to perform unintended actions via the web interface.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Feb 2021
- **Updated:** 29 May 2026
- **Also known as:** GHSA-f3x2-w4cq-5v25

## What is CVE-2021-22701?

CVE-2021-22701 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 needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A CWE-352: Cross-Site Request Forgery vulnerability exists in PowerLogic ION7400, ION7650, ION83xx/84xx/85xx/8600, ION8650, ION8800, ION9000 and PM800 (see notification for affected versions), that could cause a user to perform an unintended action on the target device when using the HTTP web interface.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

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-22701?

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

## Is CVE-2021-22701 being exploited?

There is no known exploitation of CVE-2021-22701 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-22703](https://insights.sbomify.com/CVE-2021-22703/): Information disclosure in PowerLogic ION7400, ION7650, ION83xx/84xx/85xx/8600, ION8650, ION8800, ION9000 and PM800 (see notification for affected versions) (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22701 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 needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-22701 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-22701/ (Markdown: https://insights.sbomify.com/CVE-2021-22701/index.md)
```

## Sources

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

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