dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-32303

CRITICAL · 9.3 CVSS v3.1 Published 2026-01-07
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Mojoomla WPCHURCH allows Blind SQL Injection.This issue affects WPCHURCH: from n/a through 2.7.0.

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 Mojoomla WPCHURCH WordPress plugin (versions up to 2.7.0). The vulnerability allows unauthenticated attackers to inject malicious SQL commands through unsanitized input parameters. As a blind SQL injection, attackers infer database information through boolean conditions or response timing rather than direct output, making exploitation more challenging but still highly dangerous.

MitigationUpgrade WPCHURCH plugin to the latest available version that addresses this vulnerability. If no patch is available, disable the plugin until a fix is released. Implement input validation and parameterized queries as a defense-in-depth measure.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 WPCHURCH plugin is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WPCHURCH' or 'Mojoomla WPCHURCH' in the list of installed plugins.
    Affected if The WPCHURCH plugin appears in the installed plugins list regardless of version
  2. Check installed WPCHURCH plugin version
    In the WordPress admin Plugins page, click on the plugin name or view details to display the version number. Compare this version against '2.7.0' - any version up to and including 2.7.0 is affected.
    Affected if Installed version is 2.7.0 or any earlier version (e.g., 2.6.x, 2.5.x, etc.)
  3. Verify plugin is active
    In WordPress admin > Plugins, confirm the WPCHURCH plugin status shows as 'Active'. The vulnerability is exploitable by unauthenticated attackers, so an active plugin is required for exposure.
    Affected if Plugin status shows as Active
  4. Identify exposed query parameters
    Review website access logs or use a web proxy to inspect HTTP requests sent to the WordPress site. Look for GET or POST parameters being passed to WPCHURCH plugin files (typically in /wp-content/plugins/ or through WordPress AJAX endpoints). The vulnerability exists in unsanitized input parameters.
    Affected if Any user-supplied parameters are reaching WPCHURCH plugin functionality without sanitization (general condition for SQL injection)
  5. Test for blind SQL injection behavior
    If you have access to testing capabilities, send two requests with different boolean conditions to suspected vulnerable parameters (e.g., param=1 AND 1=1 vs param=1 AND 1=2). Compare responses or response times - identical or similar responses suggest successful injection. This step requires technical security testing knowledge.
    Affected if Boolean-based or timing differences are observed in application responses indicating SQL injection is possible

A user is affected if the WPCHURCH plugin version is 2.7.0 or earlier and the plugin is active and accessible to unauthenticated users.

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 WPCHURCH plugin to the latest available version that addresses this vulnerability. If no patch is available, disable the plugin until a fix is released. Implement input validation and parameterized queries as a defense-in-depth measure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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