# CVE-2020-7527: Privilege escalation in SoMove V2.8.1 and prior

> Local attackers can gain full access to SoMove components and services due to incorrect default permissions during installation.

- **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:** 31 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v27g-f72h-2mj6

## What is CVE-2020-7527?

CVE-2020-7527 is a high-severity vulnerability in SoMove V2.8.1 and prior, published on 31 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect Default Permission vulnerability exists in SoMove (V2.8.1) and prior which could cause elevation of privilege and provide full access control to local system users to SoMove component and services when a SoMove installer script is launched.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2020-7527?

It affects 1 product.


Products: Schneider-Electric Somove.

## How do I fix CVE-2020-7527?

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

## Is CVE-2020-7527 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7527 and fix it if it is affected.

What it is: CVE-2020-7527 is a high-severity vulnerability in SoMove V2.8.1 and prior, published on 31 Aug 2020. 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-2020-7527 in the wild and no public exploit code.

Affected product: SoMove V2.8.1 and prior. 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-2020-7527/ (Markdown: https://insights.sbomify.com/CVE-2020-7527/index.md)
```

## Sources

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

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