# CVE-2017-7719: SQL injection in n/a

> SQL injection in Spider Event Calendar plugin allows attackers to manipulate database queries via the order_by parameter.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pf99-cq9r-rm44

## What is CVE-2017-7719?

CVE-2017-7719 is a critical SQL injection vulnerability in n/a, published on 12 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection in the Spider Event Calendar (aka spider-event-calendar) plugin before 1.5.52 for WordPress is exploitable with the order_by parameter to calendar_functions.php or widget_Theme_functions.php, related to front_end/frontend_functions.php.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2017-7719?

It affects 1 product.


Products: Web-Dorado Spider Event Calendar.

## How do I fix CVE-2017-7719?

No fix has been published for CVE-2017-7719 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-7719 being exploited?

There is no known exploitation of CVE-2017-7719 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7719 and fix it if it is affected.

What it is: CVE-2017-7719 is a critical SQL injection vulnerability in n/a, published on 12 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-7719 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-7719/ (Markdown: https://insights.sbomify.com/CVE-2017-7719/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7719
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7719
- OSV: https://osv.dev/vulnerability/CVE-2017-7719

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-7719/
Summaries are generated and may contain mistakes; the official description above is the record.