# CVE-2022-42972: Privilege escalation in APC Easy UPS Online Monitoring Software

> A local attacker can escalate privileges by modifying the webroot directory due to incorrect permission assignments in Schneider Electric UPS monitoring software.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2023
- **Updated:** 5 Feb 2025
- **Also known as:** GHSA-gcjp-7fh4-w3cp

## What is CVE-2022-42972?

CVE-2022-42972 is a high-severity vulnerability in Schneider Electric APC Easy UPS Online Monitoring Software, published on 1 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A CWE-732: Incorrect Permission Assignment for Critical Resource vulnerability exists that could cause local privilege escalation when a local attacker modifies the webroot directory. Affected Products: APC Easy UPS Online Monitoring Software (Windows 7, 10, 11 & Windows Server 2016, 2019, 2022 - Versions prior to V2.5-GA), APC Easy UPS Online Monitoring Software (Windows 11, Windows Server 2019, 2022 - Versions prior to V2.5-GA-01-22261), Schneider Electric Easy UPS Online Monitoring Software (Windows 7, 10, 11 & Windows Server 2016, 2019, 2022 - Versions prior to V2.5-GS), Schneider Electric Easy UPS Online Monitoring Software (Windows 11, Windows Server 2019, 2022 - Versions prior to V2.5-GS-01-22261)

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2022-42972?

It affects 2 products.


Products: Schneider-Electric Apc Easy Ups Online Monitoring Software, Schneider-Electric Easy Ups Online Monitoring Software.

## How do I fix CVE-2022-42972?

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

## Is CVE-2022-42972 being exploited?

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

## Other vulnerabilities in Schneider Electric APC Easy UPS Online Monitoring Software

- [CVE-2023-29411](https://insights.sbomify.com/CVE-2023-29411/): Missing authorization in APC Easy UPS Online Monitoring Software (Windows 10, 11 Windows Server 2016, 2019, 2022) (critical 9.8)
- [CVE-2023-29412](https://insights.sbomify.com/CVE-2023-29412/): Command injection in APC Easy UPS Online Monitoring Software (Windows 10, 11 Windows Server 2016, 2019, 2022) (critical 9.8)
- [CVE-2022-42970](https://insights.sbomify.com/CVE-2022-42970/): Missing authorization in APC Easy UPS Online Monitoring Software (critical 9.8)
- [CVE-2022-42971](https://insights.sbomify.com/CVE-2022-42971/): File upload in APC Easy UPS Online Monitoring Software (critical 9.8)
- [CVE-2022-42973](https://insights.sbomify.com/CVE-2022-42973/): Hardcoded credentials in APC Easy UPS Online Monitoring Software (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-42972 and fix it if it is affected.

What it is: CVE-2022-42972 is a high-severity vulnerability in Schneider Electric APC Easy UPS Online Monitoring Software, published on 1 Feb 2023. 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-2022-42972 in the wild and no public exploit code.

Affected product: Schneider Electric APC Easy UPS Online Monitoring Software. 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-2022-42972/ (Markdown: https://insights.sbomify.com/CVE-2022-42972/index.md)
```

## Sources

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

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