CVE-2024-8275
A public proof of concept exists; no exploitation attested.
- Published2024-09-25
- Fixed in6.6.4.1
- WeaknessCWE-89
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2024-09-2505:15CVE publishedNVD
- 2026-11-1705:17Nuclei detection templateProjectDiscovery
Versions per branch
NVD · CISA-ADP| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.6 | < 6.6.4.1 | 6.6.4.1 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.6 | ≤ 6.6.4 | no fix published | CISA-ADP |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As Wordfence, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- stellarwp The Events Calendarother versions: not affectedAffected
- ≤ 6.6.4no fix statedsemver
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-04-08
Fix
- Update Stellarwp the events calendar to 6.6.4.1
Advisories and patches
Detection
read 2026-11-01 01:02 UTC- Nuclei template
- available ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHub1 repository, unverifiedknown since 2026-11-01p33d/CVE-2024-8275
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2024-09-25
- CNACVSS 3.19.8known since 2026-10-23
- CNAweakness (CWE)CWE-89known since 2026-10-23
- FIRST EPSSEPSS score69.1 %read 2026-11-18
- PoC-in-GitHubproof of concept1known since 2026-11-01
- ProjectDiscoverydetectionread 2026-11-18
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2024-49059same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-v6x4-m48j-jm68same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2024-09-25
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
- GitHub Advisory
- GHSA-v6x4-m48j-jm68
Frequently asked questions
What is CVE-2024-8275?
Is CVE-2024-8275 actively exploited?
What is the CVSS score for CVE-2024-8275?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-v6x4-m48j-jm68
- Nuclei templates · MIT
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- PoC-in-GitHub · CC0-1.0
- CISA Vulnrichment · CC0-1.0