dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-69045

HIGH · 8.5 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in FooEvents FooEvents for WooCommerce fooevents allows SQL Injection.This issue affects FooEvents for WooCommerce: from n/a through <= 1.20.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 · moderate confidence

SQL injection vulnerability in FooEvents for WooCommerce plugin allows attackers to inject malicious SQL commands through unsanitized input parameters, potentially enabling unauthorized database access, data exfiltration, or manipulation of event and ticket data.

MitigationUpgrade FooEvents for WooCommerce to the latest patched version that implements proper input sanitization and parameterized queries; audit user-supplied data flows and implement WAF rules as interim protection.

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

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

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. Check if FooEvents for WooCommerce plugin is installed
    Inspect the WordPress plugins directory at wp-content/plugins/ for a folder named 'fooevents' or 'fooevents-for-woocommerce'. Alternatively, check the WordPress admin under Plugins > Installed Plugins for FooEvents.
    Affected if The fooevents plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress admin plugins list.
  2. Determine the installed version of FooEvents
    Open the main plugin file (usually fooevents/fooevents.php or fooevents-for-woocommerce/fooevents.php) and look for the 'Version' header in the plugin comment block. Alternatively, check the readme.txt file in the plugin folder for the 'Stable tag' entry.
    Affected if The version number found is 1.20.4 or lower (all versions through 1.20.4 are affected).
  3. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm FooEvents shows as 'Active', or query the wp_options table: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' LIKE '%fooevents%';
    Affected if The plugin is active and processing requests.
  4. Identify exposed input parameters (if accessible)
    Review plugin source code in wp-content/plugins/fooevents/ for PHP files handling $_GET, $_POST, or $_REQUEST superglobals without proper sanitization. Focus on files related to event tickets, user input processing, or database queries.
    Affected if Code analysis reveals unsanitized user input being passed to database queries, particularly in event registration or ticket handling functions.
  5. Check for suspicious database activity logs
    Review WordPress debug logs (wp-content/debug.log if enabled) and WooCommerce logs for unexpected or malformed SQL queries originating from fooevents-related actions, or monitor the database for unusual query patterns.
    Affected if Logs show SQL syntax errors or unexpected SQL fragments in queries that suggest injection attempts.

If FooEvents for WooCommerce is installed, active, and running version 1.20.4 or lower, the environment is vulnerable to CVE-2025-69045 and could be exploited via unsanitized SQL input parameters.

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 FooEvents for WooCommerce to the latest patched version that implements proper input sanitization and parameterized queries; audit user-supplied data flows and implement WAF rules as interim protection.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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