SQL InjectionWeakness · CWE-89

CVE-2026-9711

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-30

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click 7 weeks old

Official description

NVD · unedited

The EventON - WordPress Virtual Event Calendar Plugin plugin for WordPress (full) is vulnerable to SQL Injection via the WordPress 'search' parameter in versions up to, and including, 5.0.11 due to insufficient escaping on the user supplied parameter and lack of 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, granted the "Enable additional search queries" setting is enabled and at least one published event exists.

Technical summary

dbcve analysis · high confidence

The EventON WordPress plugin versions up to 5.0.11 contain an unauthenticated SQL Injection vulnerability via the 'search' parameter. The plugin fails to properly escape user input and lacks prepared statements in the SQL query, allowing attackers to inject arbitrary SQL queries when the 'Enable additional search queries' setting is enabled and at least one published event exists.

MitigationUpdate the EventON plugin to version 5.0.12 or later. As a temporary mitigation, disable the 'Enable additional search queries' setting until the update can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check EventON plugin version

In WordPress admin, go to Plugins > Installed Plugins > EventON, or check version in the plugin header file /wp-content/plugins/eventon/eventon.php. Alternatively, use WP-CLI: wp plugin list --name=eventon --format=json

Affected if Installed version is 5.0.11 or lower (any version up to and including 5.0.11)
Verify 'Enable additional search queries' setting is enabled

In WordPress admin, go to EventON > Settings > Search. Look for the 'Enable additional search queries' toggle. Alternatively, query the database: SELECT option_value FROM wp_options WHERE option_name = 'evcal_srs'

Affected if The setting is turned ON (option value indicates enabled)
Confirm published events exist

In WordPress admin, go to Events > All Events and check for any events with 'Published' status. Alternatively, query the database: SELECT COUNT(*) FROM wp_posts WHERE post_type = 'ajde_events' AND post_status = 'publish'

Affected if At least one published event exists in the database

A user is affected if they have EventON version 5.0.11 or lower WITH the 'Enable additional search queries' setting enabled AND at least one published event exists in their WordPress site.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update the EventON plugin to version 5.0.12 or later. As a temporary mitigation, disable the 'Enable additional search queries' setting until the update can be applied.

Recommended fix Moderate confidence

Version 5.0.12 or latest stable release (check WordPress plugin repository for current version)

Log in to WordPress admin dashboard
Navigate to Plugins > Installed Plugins
Locate the EventON plugin
Check for available updates or verify current version is 5.0.12 or higher
If update available, click to update the plugin to the latest stable version
Verify the update completed successfully

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing3.0 h
Review / QA2.0 h

8.0 hours of engineering $1,390

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-9711 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9711 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-9711?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 8 hrs · Moderate

Typical engagement from $1,390

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-9711 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References