How severe is CVE-2020-18164?

CVE-2020-18164 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2020-18164 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-18164?

CVE-2020-18164 affects Tp-shop. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-18164?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2020-18164 published?

CVE-2020-18164 was published on 2021-08-17 and last updated on 2026-06-17.

CVE-2020-18164

CVE-2020-18164 is a critical-severity vulnerability in Tp-shop with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-89.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 1% (63rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-89
Affected product: Tp-shop
Published: 2021-08-17
Last modified: 2026-06-17

Description

SQL Injection vulnerability exists in tp-shop 2.x-3.x via the /index.php/home/api/shop fBill parameter.

Frequently asked questions

What is CVE-2020-18164?: SQL Injection vulnerability exists in tp-shop 2.x-3.x via the /index.php/home/api/shop fBill parameter.
How severe is CVE-2020-18164?: CVE-2020-18164 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-18164 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-18164?: CVE-2020-18164 affects Tp-shop. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-18164?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2020-18164 published?: CVE-2020-18164 was published on 2021-08-17 and last updated on 2026-06-17.

References

https://xz.aliyun.com/t/5095

Affected products (1)

cpe:2.3:a:tp-shop:tp-shop:*:*:*:*:*:*:*:*

More vulnerabilities in Tp-shop

CVE-2018-9919 — Critical (CVSS 9.8): A web-accessible backdoor, with resultant SSRF, exists in Tp-shop 2.0.5 through 2.0.8, which allows remote attackers to…

All CVEs affecting Tp-shop →

Other CWE-89 (SQL Injection) vulnerabilities

CVE-2026-54350 — Critical (CVSS 10.0): Budibase is an open-source low-code platform. Prior to 3.39.12, an unauthenticated visitor of any published Budibase…
CVE-2026-8054 — Critical (CVSS 10.0): Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in the Publish Audit API endpoints…
CVE-2026-42287 — Critical (CVSS 10.0): Emlog is an open source website building system. Prior to version 2.6.11, direct SQL injection in article creation and…
CVE-2026-3325 — Critical (CVSS 10.0): SQL injection (SQLi) in MegaCMS v12.0.0, specifically in the “id_territorio” parameter of the…
CVE-2025-10878 — Critical (CVSS 10.0): A SQL injection vulnerability exists in the login functionality of Fikir Odalari AdminPando 1.0.1 before 2026-01-26.…
CVE-2025-57792 — Critical (CVSS 10.0): Explorance Blue versions prior to 8.14.9 contain a SQL injection vulnerability caused by insufficient validation of…

Browse all CWE-89 (SQL Injection) vulnerabilities →