dbcve.org
EventerWordPress extension · Imithemes

CVE-2025-0959

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-07
Fix available
A fix is available. Upgrade to 3.9.9.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 - WordPress Event & Booking Manager Plugin plugin for WordPress is vulnerable to SQL Injection via the reg_id parameter in all versions up to, and including, 3.9.9.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 authenticated attackers, with Subscriber-level access and above, 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 3.9.9.2 contain a SQL Injection vulnerability in the reg_id parameter. Authenticated attackers with Subscriber-level permissions can inject arbitrary SQL commands due to insufficient input escaping and lack of prepared statements in the SQL query, allowing extraction of sensitive database information.

MitigationUpdate the Eventer plugin to version 3.9.9.3 or later, which contains the patched code with proper SQL escaping and prepared statements. Until then, restrict subscriber-level account creation or disable the plugin.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EventerWordPress extension
Affected:< 3.9.9.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm Eventer plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'Eventer' by Imithemes, or check the plugin directory /wp-content/plugins/eventer/ for the plugin folder
    Affected if Eventer plugin is present in the WordPress installation
  2. Determine installed Eventer version
    In WordPress Admin > Plugins, find Eventer and read the version number displayed below the plugin name, or inspect /wp-content/plugins/eventer/readme.txt for the Version: field
    Affected if Version is 3.9.9.2 or lower (any version below 3.9.9.3)
  3. Verify the reg_id parameter is reachable
    Test access to the registration endpoint that uses the reg_id parameter (typically in event registration forms or event detail pages). Check if the WordPress site exposes event registration functionality accessible to authenticated users.
    Affected if Event registration forms or API endpoints accepting reg_id parameter are accessible without additional authentication beyond subscriber-level access
  4. Identify subscriber-level user accounts
    In WordPress Admin > Users, review the list of users. Click on each user to view their role under the 'Role' field in the user profile, or use wp-user-admin to query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'subscriber'
    Affected if At least one user account with Subscriber role exists on the WordPress site

You are affected if the Eventer plugin version is below 3.9.9.3 AND the event registration feature using reg_id is accessible to authenticated users with subscriber-level permissions.

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
Upgrade available Upgrade to 3.9.9.3 or later
Fixed in 3.9.9.3
Interim mitigation

Update the Eventer plugin to version 3.9.9.3 or later, which contains the patched code with proper SQL escaping and prepared statements. Until then, restrict subscriber-level account creation or disable the plugin.

Recommended fix High confidence

Eventer version 3.9.9.3

  1. 1. Create a complete backup of the WordPress site database and files
  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 version 3.9.9.3
  5. 5. Alternatively, download version 3.9.9.3 from CodeCanyon and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin version shows 3.9.9.3
  7. 7. Test event creation, booking, and registration functionality to ensure the plugin operates correctly

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

Fix this in Eventer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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-2025-0959 — 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-2025-0959 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