Security readout for executives and security teams
Plain-English summary
CVE-2016-15012 affects older Salesforce Mobile SDK for Windows 4.x apps. A SQL injection flaw in SmartStore query-count handling could let a low-privileged actor influence local app data operations. The affected product line is unsupported, so exposure should be treated as legacy technical debt requiring upgrade or retirement.
Executive priority
Prioritize remediation where legacy Windows mobile apps still handle sensitive Salesforce data. This is not presented as internet-wide or actively exploited, but unsupported dependencies reduce response options and increase long-term operational risk.
Technical view
The issue is CWE-89 SQL injection in SalesforceSDK/SmartStore/Store/QuerySpec.cs, specifically ComputeCountSql. Sources identify SalesforceMobileSDK-Windows up to 4.x as affected and version 5.0.0, with commit 83b3e91e0c1e84873a6d3ca3c5887eb5b4f5a3d8, as the fix.
Likely exposure
Exposure is likely limited to organizations still running or distributing Windows mobile applications built with forcedotcom SalesforceMobileSDK-Windows 4.x. Systems already moved to version 5.0.0 or away from this unsupported SDK are not indicated as affected by the provided sources.
Exploitation context
The CVSS vector indicates adjacent attack vector, low privileges, no user interaction, and low confidentiality, integrity, and availability impact. The source bundle does not identify active exploitation, KEV listing, exploit maturity, or public weaponization evidence.
Researcher notes
Evidence is source-limited but consistent: affected component, function, CWE, version boundary, and patch are named. The bundle does not provide exploit details, affected app configurations, or proof of exploitation, so validation should focus on dependency presence and fixed-version confirmation.
Mitigation direction
- Upgrade SalesforceMobileSDK-Windows to version 5.0.0 or later where feasible.
- Rebuild and redeploy affected Windows mobile applications after upgrading the SDK.
- Retire applications that depend on unsupported SalesforceMobileSDK-Windows 4.x components.
- Check vendor and project guidance before applying any workaround not named in sources.
Validation and detection
- Inventory Windows mobile applications using SalesforceMobileSDK-Windows.
- Confirm whether bundled SDK versions are 4.x or earlier.
- Check whether QuerySpec.cs includes the fix from commit 83b3e91e0c1e84873a6d3ca3c5887eb5b4f5a3d8.
- Verify deployed application builds were rebuilt after the SDK upgrade.
- Document any remaining unsupported SDK usage as accepted or remediated risk.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2016-15012 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.13.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://vuldb.com/?id.217619CVE reference · vdb-entry, technical-description
- https://vuldb.com/?ctiid.217619CVE reference · signature, permissions-required
- https://github.com/forcedotcom/SalesforceMobileSDK-Windows/commit/83b3e91e0c1e84873a6d3ca3c5887eb5b4f5a3d8CVE reference · patch
- https://github.com/forcedotcom/SalesforceMobileSDK-Windows/releases/tag/v5.0.0CVE reference · patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.