CVE-2019-16891

Exp

Liferay Portal CE 6.2.5 allows remote command execution because of deserialization of a JSON payload.

Published: 2019-10-04 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-16891 is rated High Exploit Risk (83.7/100): CVSS Critical severity, with high exploitation likelihood (EPSS 45.65%, 99th percentile). 3 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2019-16891

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2019-16891

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 79.56% 45.65% -33.90%
2 2026-03-13 73.43% 79.56% +6.13%
3 2026-03-04 — 73.43% —

Full EPSS history (65 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-16891

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2019-16891

GitHub Security Advisory for CVE-2019-16891

GHSA-372h-p48h-xw8q · Severity: critical · Ecosystem: maven — Liferay Portal Allows RCE via Deserialization of a JSON Payload

Affected software / configurations for CVE-2019-16891

Vendor Product Version Raw CPE
liferay liferay_portal <= 6.0.6 cpe:2.3:a:liferay:liferay_portal:*:*:*:*:community:*:*:*
liferay liferay_portal 6.1.0 cpe:2.3:a:liferay:liferay_portal:6.1.0:b1:*:*:community:*:*:*
liferay liferay_portal 6.1.0 cpe:2.3:a:liferay:liferay_portal:6.1.0:b2:*:*:community:*:*:*
liferay liferay_portal 6.1.0 cpe:2.3:a:liferay:liferay_portal:6.1.0:b3:*:*:community:*:*:*
liferay liferay_portal 6.1.0 cpe:2.3:a:liferay:liferay_portal:6.1.0:b4:*:*:community:*:*:*
liferay liferay_portal 6.1.0 cpe:2.3:a:liferay:liferay_portal:6.1.0:ga1:*:*:community:*:*:*
liferay liferay_portal 6.1.0 cpe:2.3:a:liferay:liferay_portal:6.1.0:rc1:*:*:community:*:*:*
liferay liferay_portal 6.1.1 cpe:2.3:a:liferay:liferay_portal:6.1.1:ga2:*:*:community:*:*:*
liferay liferay_portal 6.1.2 cpe:2.3:a:liferay:liferay_portal:6.1.2:ga3:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:b1:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:b2:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:ga1:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:m1:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:m2:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:m3:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:m4:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:m5:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:m6:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:rc1:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:rc2:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:rc3:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:rc4:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:rc5:*:*:community:*:*:*
liferay liferay_portal 6.2.0 cpe:2.3:a:liferay:liferay_portal:6.2.0:rc6:*:*:community:*:*:*
liferay liferay_portal 6.2.1 cpe:2.3:a:liferay:liferay_portal:6.2.1:ga2:*:*:community:*:*:*
liferay liferay_portal 6.2.2 cpe:2.3:a:liferay:liferay_portal:6.2.2:ga3:*:*:community:*:*:*
liferay liferay_portal 6.2.3 cpe:2.3:a:liferay:liferay_portal:6.2.3:ga4:*:*:community:*:*:*
liferay liferay_portal 6.2.4 cpe:2.3:a:liferay:liferay_portal:6.2.4:ga5:*:*:community:*:*:*
liferay liferay_portal 6.2.5 cpe:2.3:a:liferay:liferay_portal:6.2.5:ga6:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:a1:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:a2:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:a3:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:a4:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:a5:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:b1:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:b2:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:b3:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:b4:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:b5:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:b6:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:b7:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:ga1:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:m1:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:m2:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:m3:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:m4:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:m5:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:m6:*:*:community:*:*:*
liferay liferay_portal 7.0.0 cpe:2.3:a:liferay:liferay_portal:7.0.0:m7:*:*:community:*:*:*
liferay liferay_portal 7.0.1 cpe:2.3:a:liferay:liferay_portal:7.0.1:ga2:*:*:community:*:*:*
liferay liferay_portal 7.0.2 cpe:2.3:a:liferay:liferay_portal:7.0.2:ga3:*:*:community:*:*:*
liferay liferay_portal 7.0.3 cpe:2.3:a:liferay:liferay_portal:7.0.3:ga4:*:*:community:*:*:*
liferay liferay_portal 7.0.4 cpe:2.3:a:liferay:liferay_portal:7.0.4:ga5:*:*:community:*:*:*
liferay liferay_portal 7.0.5 cpe:2.3:a:liferay:liferay_portal:7.0.5:ga6:*:*:community:*:*:*
liferay liferay_portal 7.0.6 cpe:2.3:a:liferay:liferay_portal:7.0.6:ga7:*:*:community:*:*:*
liferay liferay_portal 7.1.0 cpe:2.3:a:liferay:liferay_portal:7.1.0:a1:*:*:community:*:*:*
liferay liferay_portal 7.1.0 cpe:2.3:a:liferay:liferay_portal:7.1.0:a2:*:*:community:*:*:*
liferay liferay_portal 7.1.0 cpe:2.3:a:liferay:liferay_portal:7.1.0:b1:*:*:community:*:*:*
liferay liferay_portal 7.1.0 cpe:2.3:a:liferay:liferay_portal:7.1.0:b2:*:*:community:*:*:*
liferay liferay_portal 7.1.0 cpe:2.3:a:liferay:liferay_portal:7.1.0:b3:*:*:community:*:*:*
liferay liferay_portal 7.1.0 cpe:2.3:a:liferay:liferay_portal:7.1.0:ga1:*:*:community:*:*:*
liferay liferay_portal 7.1.0 cpe:2.3:a:liferay:liferay_portal:7.1.0:m1:*:*:community:*:*:*
liferay liferay_portal 7.1.0 cpe:2.3:a:liferay:liferay_portal:7.1.0:m2:*:*:community:*:*:*
liferay liferay_portal 7.1.0 cpe:2.3:a:liferay:liferay_portal:7.1.0:rc1:*:*:community:*:*:*
liferay liferay_portal 7.1.1 cpe:2.3:a:liferay:liferay_portal:7.1.1:ga2:*:*:community:*:*:*
liferay liferay_portal 7.1.2 cpe:2.3:a:liferay:liferay_portal:7.1.2:ga3:*:*:community:*:*:*
liferay liferay_portal 7.1.3 cpe:2.3:a:liferay:liferay_portal:7.1.3:ga4:*:*:community:*:*:*
liferay liferay_portal 7.2.0 cpe:2.3:a:liferay:liferay_portal:7.2.0:alpha1:*:*:community:*:*:*
liferay liferay_portal 7.2.0 cpe:2.3:a:liferay:liferay_portal:7.2.0:beta1:*:*:community:*:*:*
liferay liferay_portal 7.2.0 cpe:2.3:a:liferay:liferay_portal:7.2.0:beta2:*:*:community:*:*:*
liferay liferay_portal 7.2.0 cpe:2.3:a:liferay:liferay_portal:7.2.0:beta3:*:*:community:*:*:*
liferay liferay_portal 7.2.0 cpe:2.3:a:liferay:liferay_portal:7.2.0:m2:*:*:community:*:*:*
liferay liferay_portal 7.2.0 cpe:2.3:a:liferay:liferay_portal:7.2.0:rc1:*:*:community:*:*:*
liferay liferay_portal 7.2.0 cpe:2.3:a:liferay:liferay_portal:7.2.0:rc2:*:*:community:*:*:*
liferay liferay_portal 7.2.0 cpe:2.3:a:liferay:liferay_portal:7.2.0:rc3:*:*:community:*:*:*

References for CVE-2019-16891

cvelogic Threat Intelligence