CVE-2016-15020: A vulnerability was found in liftkit database up to 2.13.1

Q: How do I fix CVE-2016-15020?

liftkit database library: upgrade to 2.13.2. Exact commands for each OS are on this page.

Q: Is CVE-2016-15020 being exploited?

CVE-2016-15020 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-15020 affect?

CVE-2016-15020 affects liftkit database library. Severity is medium (CVSS 5.5). 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 i

Q: How urgent is CVE-2016-15020?

Priority 33/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2016-15020 is a medium-severity flaw (CVSS 5.5) affecting liftkit database library. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-89
Published	2023-01-16
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: liftkit database library project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-01-16 11:15 UTCPublished CVE record published
2026-06-17 00:41 UTCUpdated Record last modified

liftkit database library project liftkit database library UPGRADE

Affected: < 2.13.2

Fixed in: 2.13.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy liftkit-database-library || rpm -q liftkit-database-library || liftkit-database-library --version

2. UPGRADE to 2.13.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade liftkit-database-library

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade liftkit-database-library

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-15020?

liftkit database library: upgrade to 2.13.2. Exact commands for each OS are on this page.

Is CVE-2016-15020 being exploited?

CVE-2016-15020 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-15020 affect?

CVE-2016-15020 affects liftkit database library. Severity is medium (CVSS 5.5). 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 i

How urgent is CVE-2016-15020?

Priority 33/100. No elevated risk signals yet.

Software pages

PHP vulnerabilities

References

← Back to latest CVEs