CVE-2026-49772
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Liquid Web / StellarWP The Events Calendar allows Blind SQL Injection. This issue affects The Events Calendar: from 6.15.12 through 6.16.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA blind SQL injection vulnerability exists in The Events Calendar WordPress plugin versions 6.15.12 through 6.16.2. The vulnerability allows remote attackers to inject malicious SQL commands via unsanitized user input that is directly incorporated into SQL queries, enabling data exfiltration or database manipulation through blind injection techniques.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm The Events Calendar plugin is installedNavigate to WordPress Admin > Plugins and locate 'The Events Calendar' in the list of installed plugins, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins'Affected if The plugin does not appear in the installed plugins list (not vulnerable if not installed)
-
Check the installed version numberIn WordPress Admin, go to Plugins > Installed Plugins > The Events Calendar and read the version number displayed, or query: SELECT option_value FROM wp_options WHERE option_name = 'tribe_events_version'Affected if The version is 6.15.12, 6.15.13, 6.15.14, 6.16.0, 6.16.1, or 6.16.2 (any version from 6.15.12 through 6.16.2 inclusive)
-
Verify the plugin is activeIn WordPress Admin > Plugins, confirm The Events Calendar shows as 'Active' rather than 'Inactive' or 'Network Active'Affected if The plugin is currently active (inactive plugins do not expose the vulnerability)
-
Check for event-related user input functionalityReview the website for publicly accessible event submission forms, event search/filter features, or calendar views that accept URL parameters (common vectors for SQL injection in event plugins)Affected if The site uses event features that process user-supplied input in URLs or forms
-
Examine web server and application logs for suspicious SQL patternsSearch access logs (typically in /var/log/nginx/ or /var/log/apache2/) for unusual SQL keywords (UNION, SELECT, WHERE, OR 1=1) in request parameters, especially on pages under /events/ or /tribe/ pathsAffected if Log analysis reveals SQL injection attempts or unusual database query patterns in requests
A user is affected if The Events Calendar plugin is installed, active, and running version 6.15.12 through 6.16.2 with event features that accept user input exposed on the site.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate The Events Calendar plugin to version 6.16.2 or later to obtain the patched code that properly sanitizes database inputs. If immediate update is not possible, consider disabling the affected plugin or implementing a WAF rule to block SQL injection attempts.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49772 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data