dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-28939

HIGH · 8.5 CVSS v3.1 Published 2025-03-26
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 EuroCizia WP Google Calendar Manager wp-gcalendar allows Blind SQL Injection.This issue affects WP Google Calendar Manager: from n/a through <= 2.1.

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

A blind SQL injection vulnerability exists in the WP Google Calendar Manager WordPress plugin (versions <= 2.1). The vulnerability allows unauthenticated attackers to inject malicious SQL queries through improper neutralization of special elements in SQL commands. As a blind SQL injection, attackers infer results through behavioral differences rather than direct output.

MitigationUpdate WP Google Calendar Manager to the latest patched version available from the vendor. If no patched version exists, disable the plugin until a fix is released, or implement input validation/parameterized queries at the application layer.

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. Confirm WP Google Calendar Manager plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WP Google Calendar Manager' in the installed plugins list, or search the wp-content/plugins directory for a folder named 'wp-google-calendar-manager' or similar.
    Affected if The plugin appears in the installed plugins list regardless of activation status
  2. Identify the installed plugin version
    In WordPress admin > Plugins, find WP Google Calendar Manager and click on the plugin name to view the version number displayed in the plugin details, or inspect the plugin's main PHP file header for the 'Version' tag.
    Affected if The displayed version number is 2.1 or any version lower than 2.1
  3. Check if the plugin is active
    In WordPress admin > Plugins, verify whether WP Google Calendar Manager shows as 'Active' under the plugin status column.
    Affected if The plugin is active and the version is 2.1 or lower - this makes the vulnerable code reachable
  4. Identify publicly accessible endpoints handling plugin functionality
    Review the plugin's AJAX endpoints (usually in admin-ajax.php with 'wp_ajax_' or 'wp_ajax_nopriv_' hooks) or any direct request handlers that process user-supplied parameters, especially those used in calendar or event display functionality.
    Affected if The plugin exposes endpoints accessible to unauthenticated users (no login required) that process parameters without proper SQL escaping

You are affected if the WP Google Calendar Manager plugin is installed, active, and running at version 2.1 or lower, as this version range contains the blind SQL injection vulnerability in unauthenticated-accessible code paths.

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 WP Google Calendar Manager to the latest patched version available from the vendor. If no patched version exists, disable the plugin until a fix is released, or implement input validation/parameterized queries at the application layer.

Recommended fix Moderate confidence

A version of WP Google Calendar Manager greater than 2.1 (specific fixed release version unknown from available data)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Check if a newer version of WP Google Calendar Manager plugin is available in the WordPress plugin repository.
  3. 3. If a newer version (greater than 2.1) is available, update the plugin through WordPress admin > Plugins > Updates, or manually upload the new version.
  4. 4. If no update is available from the official repository, contact the plugin developer directly to request a security patch for CVE-2025-28939.
  5. 5. Consider temporarily disabling the WP Google Calendar Manager plugin if no fix is available and you cannot wait for a patch.
  6. 6. After updating, verify the fix by testing the calendar functionality and monitoring for any unusual database behavior.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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