LiveActive security incident?Get immediate response
CVE Record

CVE-2016-15020: liftkit database Query.php processOrderBy sql injection

A vulnerability was found in liftkit database up to 2.13.1. It has been classified as critical. This affects the function processOrderBy of the file src/Query/Query.php. The manipulation leads to sql injection. Upgrading to version 2.13.2 is able to address this issue. The patch is named 42ec8f2b22e0b0b98fb5b4444ed451c1b21d125a. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-218391.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2016-15020 is a SQL injection issue in liftkit/database versions 2.13.0 and 2.13.1. It affects order-by query handling and could let an authenticated user influence database queries if an application exposes that path. The provided sources identify version 2.13.2 as the fix.

Executive priority

Address during normal vulnerability remediation unless the affected library is used in sensitive applications or exposed to broad authenticated users. Escalate if business data integrity or customer-facing workflows depend on affected ordering queries.

Technical view

The issue is mapped to CWE-89 in src/Query/Query.php, function processOrderBy. The CVSS 3.1 vector is AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, score 5.5. Sources cite patch commit 42ec8f2b22e0b0b98fb5b4444ed451c1b21d125a and release v2.13.2.

Likely exposure

Exposure appears limited to applications using liftkit/database 2.13.0 or 2.13.1 where a privileged or authenticated user can affect order-by inputs. The CVSS vector indicates adjacent network access and low privileges are required.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation evidence. VulDB classifies the issue as critical, while the supplied CVSS score is medium. Treat exploit status as unconfirmed from these sources.

Researcher notes

Evidence is specific to liftkit/database processOrderBy and the v2.13.2 patch. The bundle does not provide proof-of-concept detail, observed exploitation, or downstream product impact, so exposure must be confirmed through dependency and code-path review.

Mitigation direction

  • Upgrade liftkit/database to version 2.13.2.
  • Prioritize systems using versions 2.13.0 or 2.13.1.
  • Review the referenced patch and release notes before deployment.
  • If upgrade is delayed, check vendor guidance for interim handling.

Validation and detection

  • Inventory package manifests and lockfiles for liftkit/database versions.
  • Confirm deployed systems are no longer on 2.13.0 or 2.13.1.
  • Verify the patched processOrderBy implementation is present.
  • Review application paths that expose sort or order controls.
  • Run regression tests for database ordering behavior after upgrade.
Prepared
Confidence
high
Sources
6

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

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

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

CVE-2016-15020 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
5Source 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-15020Attack 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
liftkitdatabase2.13.0, 2.13.1Listed
Weakness

CWE details

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

CWE-89 · source CWE mapping

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.