How severe is CVE-2017-20160?

CVE-2017-20160 has a CVSS 3.x base score of 6.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.

Is CVE-2017-20160 being actively exploited?

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

What products are affected by CVE-2017-20160?

CVE-2017-20160 affects Flitto Express-param. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-20160?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2017-20160 published?

CVE-2017-20160 was published on 2022-12-31 and last updated on 2026-06-17.

CVE-2017-20160

CVE-2017-20160 is a medium-severity vulnerability in Flitto Express-param with a CVSS 3.x base score of 6.3. 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-235.

Key facts

Severity: Medium (CVSS 3.x base score 6.3)
CVSS v2: 6.5
EPSS exploit prediction: 1% (52nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-235
Affected product: Flitto Express-param
Published: 2022-12-31
Last modified: 2026-06-17

Description

A vulnerability was found in flitto express-param up to 0.x. It has been classified as critical. This affects an unknown part of the file lib/fetchParams.js. The manipulation leads to improper handling of extra parameters. It is possible to initiate the attack remotely. Upgrading to version 1.0.0 is able to address this issue. The identifier of the patch is db94f7391ad0a16dcfcba8b9be1af385b25c42db. It is recommended to upgrade the affected component. The identifier VDB-217149 was assigned to this vulnerability.

Frequently asked questions

What is CVE-2017-20160?: A vulnerability was found in flitto express-param up to 0.x. It has been classified as critical. This affects an unknown part of the file lib/fetchParams.js. The manipulation leads to improper handling of extra parameters. It is possible to initiate the attack remotely. Upgrading to version 1.0.0 is able to address this issue. The identifier of the patch is db94f7391ad0a16dcfcba8b9be1af385b25c42db. It is recommended to upgrade the affected component. The identifier VDB-217149 was assigned to this vulnerability.
How severe is CVE-2017-20160?: CVE-2017-20160 has a CVSS 3.x base score of 6.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
Is CVE-2017-20160 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-20160?: CVE-2017-20160 affects Flitto Express-param. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-20160?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2017-20160 published?: CVE-2017-20160 was published on 2022-12-31 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:flitto:express-param:*:*:*:*:*:*:*:*

Other CWE-235 vulnerabilities

CVE-2026-27851 — High (CVSS 7.4): When safe filter is used with variable expansion, all following pipelines on the same string are incorrectly…
CVE-2026-20083 — Medium (CVSS 6.5): A vulnerability in the Secure Copy Protocol (SCP) server feature of Cisco IOS XE Software could allow an authenticated,…
CVE-2024-47651 — Medium (CVSS 6.5): This vulnerability exists in Shilpi Client Dashboard due to improper handling of multiple parameters in the API…

Browse all CWE-235 vulnerabilities →