LiveActive security incident?Get immediate response
CVE Record

CVE-2016-15007: Centralized-Salesforce-Dev-Framework SOQL SObjectService.cls SObjectService injection

A vulnerability was found in Centralized-Salesforce-Dev-Framework. It has been declared as problematic. Affected by this vulnerability is the function SObjectService of the file src/classes/SObjectService.cls of the component SOQL Handler. The manipulation of the argument orderDirection leads to injection. The patch is named db03ac5b8a9d830095991b529c067a030a0ccf7b. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-217195.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Salesforce framework bug where a sorting direction parameter could be injected into a SOQL handler. The reported impact is medium: an authenticated adjacent actor could affect confidentiality, integrity, and availability at low levels. No KEV listing or provided source shows active exploitation.

Executive priority

Handle as a moderate application-layer issue. It does not justify emergency response from the supplied evidence, but teams using this Salesforce framework should patch or verify forks during the next vulnerability remediation cycle.

Technical view

CVE-2016-15007 affects SObjectService in src/classes/SObjectService.cls of Centralized-Salesforce-Dev-Framework's SOQL Handler. Manipulation of orderDirection leads to injection. The CVSS 3.1 score is 5.5 with adjacent access, low complexity, low privileges, and no user interaction.

Likely exposure

Organizations with Salesforce custom code based on or forked from Centralized-Salesforce-Dev-Framework, especially where SObjectService accepts user-controlled orderDirection. Published data does not identify package versions or CPEs, so exposure must be confirmed by code inventory rather than product scans.

Exploitation context

The provided sources describe the issue and identify required privileges, but they do not show exploitation in the wild. It is not listed as KEV in the supplied bundle. Treat exploit status as unconfirmed unless new vendor or threat-intelligence evidence appears.

Researcher notes

Evidence is narrow: VulDB identifies CWE-74 injection in orderDirection and the GitHub commit as the patch. Version ranges and CPEs are not provided. Research should focus on code provenance, patched-vs-unpatched SObjectService behavior, and reachable callers.

Mitigation direction

  • Apply the referenced patch commit db03ac5b8a9d830095991b529c067a030a0ccf7b.
  • Check project or vendor guidance for any newer supported remediation.
  • Treat local forks as affected until SObjectService.cls matches the patched behavior.
  • Prioritize deployments where orderDirection can be influenced by authenticated users.

Validation and detection

  • Inventory Salesforce repositories for Centralized-Salesforce-Dev-Framework or derived SObjectService.cls code.
  • Compare src/classes/SObjectService.cls against the referenced patched commit.
  • Trace whether orderDirection is built from request, UI, API, or integration input.
  • Confirm tests cover allowed and rejected sort-direction values.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-74: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2016-15007 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.13.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2016-15007Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aCentralized-Salesforce-Dev-Frameworkn/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-74 · source CWE mapping

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.