How severe is CVE-2017-17616?

CVE-2017-17616 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-2017-17616 being actively exploited?

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

What products are affected by CVE-2017-17616?

CVE-2017-17616 affects Event Calendar Category Script Project Event Calendar Category Script. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-17616?

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-2017-17616 published?

CVE-2017-17616 was published on 2017-12-13 and last updated on 2026-06-17.

CVE-2017-17616

CVE-2017-17616 is a critical-severity vulnerability in Event Calendar Category Script Project Event Calendar Category Script 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: 3% (86th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-89
Affected product: Event Calendar Category Script Project Event Calendar Category Script
Published: 2017-12-13
Last modified: 2026-06-17

Description

Event Search Script 1.0 has SQL Injection via the /event-list city parameter.

Frequently asked questions

What is CVE-2017-17616?: Event Search Script 1.0 has SQL Injection via the /event-list city parameter.
How severe is CVE-2017-17616?: CVE-2017-17616 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-2017-17616 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (86th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-17616?: CVE-2017-17616 affects Event Calendar Category Script Project Event Calendar Category Script. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-17616?: 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-2017-17616 published?: CVE-2017-17616 was published on 2017-12-13 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:event_calendar_category_script_project:event_calendar_category_script:1.0:*:*:*:*:*:*:*

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 →