# CVE-2024-8275: The Events Calendar <= 6.6.4 - Unauthenticated SQL Injection

> Unauthenticated attackers can extract sensitive database information via SQL injection in The Events Calendar plugin if the vulnerable function is manually used.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 25 Sep 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-v6x4-m48j-jm68

## What is CVE-2024-8275?

CVE-2024-8275 is a critical SQL injection vulnerability in stellarwp The Events Calendar, published on 25 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The The Events Calendar plugin for WordPress is vulnerable to SQL Injection via the 'order' parameter of the 'tribe_has_next_event' function in all versions up to, and including, 6.6.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Only sites that have manually added tribe_has_next_event() will be vulnerable to this SQL injection.

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

## Which versions are affected by CVE-2024-8275?

It affects 1 product.


Products: Stellarwp the Events Calendar.

## How do I fix CVE-2024-8275?

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

## Is CVE-2024-8275 being exploited?

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

Public exploit code:

- https://github.com/p33d/CVE-2024-8275 (github_poc): https://github.com/p33d/CVE-2024-8275

## Other vulnerabilities in stellarwp The Events Calendar

- [CVE-2024-4180](https://insights.sbomify.com/CVE-2024-4180/): The Events Calendar < 6.4.0.1 - Reflected XSS (critical 9.1)
- [CVE-2023-6203](https://insights.sbomify.com/CVE-2023-6203/): The Events Calendar < 6.2.8.1 - Unauthenticated Arbitrary Password Protected Post Read (high 7.5)
- [CVE-2024-6931](https://insights.sbomify.com/CVE-2024-6931/): The Events Calendar <= 6.6.3 - Unauthenticated Stored Cross-Site Scripting (high 7.2)
- [CVE-2025-5144](https://insights.sbomify.com/CVE-2025-5144/): The Events Calendar <= 6.13.2 - Authenticated (Contributor+) DOM-Based Stored Cross-Site Scripting (medium 6.4)
- [CVE-2019-15109](https://insights.sbomify.com/CVE-2019-15109/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8275 and fix it if it is affected.

What it is: CVE-2024-8275 is a critical SQL injection vulnerability in stellarwp The Events Calendar, published on 25 Sep 2024. 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-2024-8275 in the wild and no public exploit code.

Affected product: stellarwp The Events Calendar. 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-2024-8275/ (Markdown: https://insights.sbomify.com/CVE-2024-8275/index.md)
```

## Sources

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

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