dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10587

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-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

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 Community Events plugin for WordPress is vulnerable to SQL Injection via the event_category parameter in all versions up to, and including, 1.5.1 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 Community Events WordPress plugin (versions up to 1.5.1) contains a SQL injection vulnerability in the event_category parameter. The plugin fails to properly escape user input and does not use prepared SQL statements, allowing authenticated attackers with Subscriber-level access or higher to inject arbitrary SQL commands and extract sensitive database information.

MitigationUpdate the Community Events plugin to the latest version immediately. If no patched version exists, manually remediate by replacing direct SQL concatenation with $wpdb->prepare() for the event_category parameter and ensure all user-supplied values are properly escaped before database queries.

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 Community Events plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Community Events' plugin, or query the wp_options table for option_name = 'active_plugins' and search for 'community-events' in the serialized array
    Affected if The Community Events plugin appears in the list of active plugins
  2. Check the installed plugin version
    In WordPress admin Plugins page, click on the Community Events plugin to view its details and note the version number. Compare it to the affected range: versions up to and including 1.5.1 are vulnerable
    Affected if The installed version is 1.5.1 or lower
  3. Confirm user role access to the vulnerable feature
    Check if any user role of Subscriber or higher exists in WordPress (Users > All Users). The vulnerability is exploitable by any authenticated user with Subscriber-level access or higher
    Affected if There are users with Subscriber-level access or higher who can access the site
  4. Identify if event_category parameter handling is present
    Inspect the plugin files for code handling the 'event_category' parameter, particularly in AJAX handlers or request processing logic. Look for SQL queries that incorporate this parameter directly without prepared statements
    Affected if The plugin processes the event_category parameter in database queries without using $wpdb->prepare() or equivalent prepared statements

You are affected if the Community Events plugin is active, the version is 1.5.1 or lower, and authenticated users with Subscriber-level access can trigger the event_category parameter in database queries that lack prepared statements.

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 Community Events plugin to the latest version immediately. If no patched version exists, manually remediate by replacing direct SQL concatenation with $wpdb->prepare() for the event_category parameter and ensure all user-supplied values are properly escaped before database queries.

Recommended fix Moderate confidence

Community Events plugin version 1.5.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Community Events plugin
  4. Check if an update is available - if so, click 'Update Now'
  5. Alternatively, manually download version 1.5.2 or later from wordpress.org/plugins/community-events/
  6. Deactivate the old version, delete it, then upload and activate the new version
  7. Verify the update was successful by checking the plugin version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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