dbcve.org
CWE-289Weakness · CWE-289

CVE-2026-9701

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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 an insecure password reset mechanism in all versions up to, and including, 4.4.2. The plugin stores a plaintext copy of the password reset key in the `eventer_verification_code` user meta field when a user requests a password reset. The plaintext key stored in `wp_usermeta` can be used with the plugin's custom reset action to set a new password for any user. Combined with another vulnerability such as SQL Injection (CVE-2026-9700), this makes it possible for unauthenticated attackers to extract the plaintext reset key and take over any user account, including administrators. Note: The password reset function only works up to PHP version 7.4.

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) stores plaintext password reset tokens in the `eventer_verification_code` user meta field. Attackers who obtain these tokens (e.g., via SQL injection CVE-2026-9700) can use the plugin's custom reset action to set new passwords for any user account, including administrators. This attack vector is limited to PHP versions 7.4 and below.

MitigationUpgrade to a patched version of the Eventer plugin once available; until then, disable the plugin, ensure PHP version is above 7.4 as a partial mitigation, and address any accompanying SQL injection vulnerabilities (CVE-2026-9700).

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
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? 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
    Navigate to WordPress admin > Plugins and locate the Eventer plugin, or check the plugin file header in wp-content/plugins/eventer/eventer.php for the 'Version' declared value
    Affected if Eventer plugin is installed and version is 4.4.2 or below, or the version cannot be determined (assume vulnerable)
  2. Determine PHP version
    Run 'php -v' from command line, check phpinfo(), or review server configuration files; confirm whether PHP version is 7.4 or below
    Affected if PHP version is 7.4 or below (the vulnerability only affects these versions)
  3. Inspect eventer_verification_code meta field
    Query the WordPress usermeta table for any records where meta_key = 'eventer_verification_code' and meta_value is non-empty, using: SELECT * FROM wp_usermeta WHERE meta_key = 'eventer_verification_code'; (adjust prefix if different)
    Affected if Any user meta records exist with populated eventer_verification_code values (plaintext tokens are present)
  4. Review password reset activity logs
    Check WordPress audit logs, server access logs, or security plugins for entries involving 'eventer_reset_password' action or unusual password changes on administrative accounts
    Affected if Password reset actions via the Eventer plugin are logged, especially for administrator accounts not initiated by the legitimate user

User is affected if Eventer plugin version 4.4.2 or below is installed, PHP is version 7.4 or below, and plaintext verification tokens exist in the eventer_verification_code user meta field.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of the Eventer plugin once available; until then, disable the plugin, ensure PHP version is above 7.4 as a partial mitigation, and address any accompanying SQL injection vulnerabilities (CVE-2026-9700).

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9701 — 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-9701 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