# CVE-2022-40615: IBM Sterling Partner Engagement Manager SQL injection

> A remote attacker can exploit SQL injection in IBM Sterling Partner Engagement Manager to view, add, modify, or delete back-end database information.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 11 Jan 2023
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-v3vj-pm98-82mp

## What is CVE-2022-40615?

CVE-2022-40615 is a medium-severity SQL injection vulnerability in IBM Sterling Partner Engagement Manager, published on 11 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Sterling Partner Engagement Manager 6.1, 6.2, and 6.2.1 is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 236208.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Ibm Sterling Partner Engagement Manager.

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

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

## Is CVE-2022-40615 being exploited?

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

## Other vulnerabilities in IBM Sterling Partner Engagement Manager

- [CVE-2025-33093](https://insights.sbomify.com/CVE-2025-33093/): IBM Sterling Partner Engagement Manager information disclosure (high 7.5)
- [CVE-2022-35639](https://insights.sbomify.com/CVE-2022-35639/): Denial of service in Sterling Partner Engagement Manager (high 7.5)
- [CVE-2022-34348](https://insights.sbomify.com/CVE-2022-34348/): XML external entity in Partner Engagement Manager (high 7.1)
- [CVE-2022-34335](https://insights.sbomify.com/CVE-2022-34335/): IBM Sterling Partner Engagement Manager denial of service (medium 6.5)
- [CVE-2023-38722](https://insights.sbomify.com/CVE-2023-38722/): IBM Sterling Partner Engagement Manager cross-site scripting (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40615 is a medium-severity SQL injection vulnerability in IBM Sterling Partner Engagement Manager, published on 11 Jan 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-40615 in the wild and no public exploit code.

Affected product: IBM Sterling Partner Engagement Manager. 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-40615/ (Markdown: https://insights.sbomify.com/CVE-2022-40615/index.md)
```

## Sources

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

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