# CVE-2023-47256: Security feature bypass in n/a

> Local users can bypass security controls to connect to arbitrary relay servers due to implicit trust in proxy settings.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-pgq6-4q3w-7pvf

## What is CVE-2023-47256?

CVE-2023-47256 is a medium-severity vulnerability in n/a, published on 1 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ConnectWise ScreenConnect through 23.8.4 allows local users to connect to arbitrary relay servers via implicit trust of proxy settings

Weakness: CWE-287 (Improper Authentication)

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

It affects 2 products.


Products: Connectwise Automate, Connectwise Screenconnect.

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

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

## Is CVE-2023-47256 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-35066](https://insights.sbomify.com/CVE-2021-35066/): XML external entity in n/a (critical 9.8)
- [CVE-2020-15027](https://insights.sbomify.com/CVE-2020-15027/): Auth bypass in n/a (critical 9.8)
- [CVE-2025-11492](https://insights.sbomify.com/CVE-2025-11492/): HTTP Configuration and Encryption in Transit (critical 9.6)
- [CVE-2026-9089](https://insights.sbomify.com/CVE-2026-9089/): Supply chain in Automate (high 8.8)
- [CVE-2025-11493](https://insights.sbomify.com/CVE-2025-11493/): Self-Update Verification Mechanism Process in ConnectWise Automate (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-47256 is a medium-severity vulnerability in n/a, published on 1 Feb 2024. 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-2023-47256 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-47256/ (Markdown: https://insights.sbomify.com/CVE-2023-47256/index.md)
```

## Sources

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

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