# CVE-2022-47542: Privilege escalation in n/a

> Remote attackers can escalate privileges in Red Gate SQL Monitor due to incorrect access control, requiring an upgrade to secure the system.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2023
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-2qrx-mpvp-j33p

## What is CVE-2022-47542?

CVE-2022-47542 is a high-severity vulnerability in n/a, published on 30 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Red Gate SQL Monitor 11.0.14 through 12.1.46 has Incorrect Access Control, exploitable remotely for Escalation of Privileges.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Red-Gate Sql Monitor.

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

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

## Is CVE-2022-47542 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-9098](https://insights.sbomify.com/CVE-2015-9098/): SQL injection in n/a (critical 9.8)
- [CVE-2020-9318](https://insights.sbomify.com/CVE-2020-9318/): SQL injection in n/a (high 7.2)
- [CVE-2022-47870](https://insights.sbomify.com/CVE-2022-47870/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2020-15526](https://insights.sbomify.com/CVE-2020-15526/): Security feature bypass in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47542 is a high-severity vulnerability in n/a, published on 30 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-47542 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-2022-47542/ (Markdown: https://insights.sbomify.com/CVE-2022-47542/index.md)
```

## Sources

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

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