dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-9700

HIGH · 7.5 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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 · unedited
The Eventer plugin for WordPress is vulnerable to time-based SQL Injection via the ‘code’ parameter in all versions up to, and including, 4.4.2 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.

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 confidence

The Eventer WordPress plugin versions up to 4.4.2 contain a time-based SQL injection vulnerability in the 'code' parameter. The plugin fails to properly escape user input and lacks prepared statements, allowing unauthenticated attackers to inject arbitrary SQL queries to extract sensitive data from the database.

MitigationUpdate the Eventer plugin to a version beyond 4.4.2 once available, or disable the plugin until a patch is released. If immediate remediation is required, implement input validation and convert the vulnerable queries to use prepared statements.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 checks

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

  1. Verify Eventer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Eventer' in the list. Alternatively, check the file /wp-content/plugins/eventer/ for the plugin directory.
    Affected if Eventer plugin is present in the WordPress installation
  2. Check installed Eventer version
    In WordPress admin, go to Plugins > Installed Plugins, find Eventer, and view the version number displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/eventer/eventer.php for the 'Version' tag.
    Affected if Version is 4.4.2 or lower, or if the version cannot be determined and the plugin is present
  3. Confirm the vulnerable code parameter is in use
    The vulnerability affects the 'code' parameter in the plugin's functionality. Identify if the plugin's features that use a 'code' parameter are active or accessible on the site. This may require reviewing plugin shortcodes, templates, or public-facing features that accept a 'code' input.
    Affected if The plugin is active and the 'code' parameter functionality is accessible without authentication

You are affected if the Eventer plugin is installed, the version is 4.4.2 or lower, and the vulnerable 'code' parameter feature is accessible on your site.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Eventer plugin to a version beyond 4.4.2 once available, or disable the plugin until a patch is released. If immediate remediation is required, implement input validation and convert the vulnerable queries to use prepared statements.

Recommended fix Moderate confidence

Eventer version 4.4.3 or later

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the Eventer plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the updated plugin from a trusted source (such as the official WordPress repository or codecanyon.net)
  6. 6. Deactivate the old version of the plugin before reinstalling if automatic update fails
  7. 7. After updating, verify the plugin is functioning correctly and test that the 'code' parameter is properly handled

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9700 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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