# CVE-2023-26918: Privilege escalation in n/a

> Attackers can escalate privileges to LocalSystem by replacing files in a directory with excessive Everyone write permissions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2023
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-w8c5-v27m-v5ch

## What is CVE-2023-26918?

CVE-2023-26918 is a critical vulnerability in n/a, published on 13 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Diasoft File Replication Pro 7.5.0 allows attackers to escalate privileges by replacing a legitimate file with a Trojan horse that will be executed as LocalSystem. This occurs because %ProgramFiles%\FileReplicationPro allows Everyone:(F) access.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2023-26918?

It affects 1 product.


Products: Filereplicationpro File Replication Pro.

## How do I fix CVE-2023-26918?

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

## Is CVE-2023-26918 being exploited?

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

Public exploit code:

- File Replication Pro 7.5.0 - Privilege Escalation/Password reset due Incorrect Access Control (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26918 and fix it if it is affected.

What it is: CVE-2023-26918 is a critical vulnerability in n/a, published on 13 Apr 2023. 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-2023-26918 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-2023-26918/ (Markdown: https://insights.sbomify.com/CVE-2023-26918/index.md)
```

## Sources

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

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