# CVE-2016-15012: forcedotcom SalesforceMobileSDK-Windows QuerySpec.cs ComputeCountSql sql injection


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Jan 2023
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-r3hc-3x59-gp9x

## What is CVE-2016-15012?

CVE-2016-15012 is a medium-severity vulnerability in forcedotcom SalesforceMobileSDK-Windows, published on 7 Jan 2023. 

### Official description

** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in forcedotcom SalesforceMobileSDK-Windows up to 4.x. It has been rated as critical. This issue affects the function ComputeCountSql of the file SalesforceSDK/SmartStore/Store/QuerySpec.cs. The manipulation leads to sql injection. Upgrading to version 5.0.0 is able to address this issue. The patch is named 83b3e91e0c1e84873a6d3ca3c5887eb5b4f5a3d8. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-217619. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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

## Which versions are affected by CVE-2016-15012?

It affects 1 product.


Products: Salesforce Mobile Software Development Kit.

## How do I fix CVE-2016-15012?

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

## Is CVE-2016-15012 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-15012 and fix it if it is affected.

What it is: CVE-2016-15012 is a medium-severity vulnerability in forcedotcom SalesforceMobileSDK-Windows, published on 7 Jan 2023. 
Exploitation: There is no known exploitation of CVE-2016-15012 in the wild and no public exploit code.

Affected product: forcedotcom SalesforceMobileSDK-Windows. 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-2016-15012/ (Markdown: https://insights.sbomify.com/CVE-2016-15012/index.md)
```

## Sources

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

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