dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-3180

HIGH · 7.5 CVSS v3.1 Published 2026-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Contest Gallery – Upload & Vote Photos, Media, Sell with PayPal & Stripe plugin for WordPress is vulnerable to blind SQL Injection via the ‘cgLostPasswordEmail’ and the ’cgl_mail’ parameter in all versions up to, and including, 28.1.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The vulnerability's ’cgLostPasswordEmail’ parameter was patched in version 28.1.4, and the ’cgl_mail’ parameter was patched in version 28.1.5.

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

Blind SQL Injection vulnerability in the Contest Gallery WordPress plugin allows unauthenticated attackers to inject arbitrary SQL queries via the 'cgLostPasswordEmail' and 'cgl_mail' parameters due to insufficient input escaping and lack of prepared statements in the SQL queries. This enables extraction of sensitive database information.

MitigationUpdate the Contest Gallery plugin to version 28.1.5 or later to receive the patched code that properly escapes user input and implements prepared SQL statements.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Contest Gallery plugin is installed
    Locate the Contest Gallery plugin folder in wp-content/plugins/ and check for the main plugin file (usually contest-gallery.php or similar)
    Affected if The plugin folder and main PHP file exist in the WordPress plugins directory
  2. Determine installed plugin version
    Open the main plugin PHP file and locate the version comment/constant (typically 'Version: x.x.x' or defined version constant)
    Affected if The version number found is lower than 28.1.5
  3. Confirm the plugin is active
    Check WordPress database wp_options table for option_name containing 'active_plugins' or use WP admin to verify plugin status
    Affected if The plugin appears in the list of active plugins
  4. Identify exposed vulnerable endpoints
    Check if the lost password form is accessible on the frontend (usually at /wp-login.php?action=lostpassword or a custom contest gallery lost password page) and verify the 'cgLostPasswordEmail' and 'cgl_mail' parameters are accepted
    Affected if The lost password functionality is active and accepts user input without authentication

The environment is affected if Contest Gallery plugin version is below 28.1.5, the plugin is active, and the lost password form with the vulnerable parameters is accessible on the site.

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 Contest Gallery plugin to version 28.1.5 or later to receive the patched code that properly escapes user input and implements prepared SQL statements.

Recommended fix High confidence

Contest Gallery plugin version 28.1.5 or later

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Find the 'Contest Gallery' plugin in the list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 28.1.5 or later.
  5. 5. Alternatively, you can manually download the latest version from wordpress.org/plugins/contest-gallery/ and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is running version 28.1.5 or higher under Plugins > Installed Plugins.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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