dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-57662

HIGH · 8.5 CVSS v3.1 Published 2026-06-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 8 weeks old

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
Contributor SQL Injection in Contest Gallery <= 30.0.0 versions.

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 the Contest Gallery WordPress plugin (versions <= 30.0.0) allows authenticated users with Contributor-level permissions to inject malicious SQL queries through unsanitized input parameters, potentially enabling unauthorized data exfiltration or database manipulation.

MitigationUpdate Contest Gallery plugin to a version beyond 30.0.0 when available, or apply vendor-supplied security patches; alternatively, restrict or disable the plugin until remediation is possible.

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. Verify Contest Gallery plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Contest Gallery. Check the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file header or version.php for the version constant.
    Affected if The installed version is 30.0.0 or lower.
  2. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that Contest Gallery shows as 'Active' rather than 'Inactive'.
    Affected if The plugin is active and version is 30.0.0 or lower.
  3. Identify exposed contest gallery functionality
    Check pages, posts, or widgets containing Contest Gallery shortcodes (commonly [contest_gallery], [cg_...], or custom contest IDs). Search database wp_postmeta for meta_key containing 'contest' or review published content with gallery contests.
    Affected if Contest Gallery shortcodes or forms are published and accessible to logged-in users.
  4. Audit user role permissions
    In WordPress admin under Users, review which users have the Contributor role. Also check if any custom roles with similar capabilities exist. Contributors can create and edit posts but cannot publish.
    Affected if One or more users have Contributor-level permissions, and they can access contest gallery functionality.
  5. Inspect plugin input handling (optional)
    If you have file access, examine the plugin source code for $_GET, $_POST, or $_REQUEST usage in contest-related files without proper prepare() statements or sanitization functions like esc_sql() or $wpdb->prepare().
    Affected if Unsanitized input parameters are present in contest-related code.

Your environment is likely affected if Contest Gallery plugin version 30.0.0 or lower is active and you have Contributor-level users who can access contest functionality that accepts user input.

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

Update Contest Gallery plugin to a version beyond 30.0.0 when available, or apply vendor-supplied security patches; alternatively, restrict or disable the plugin until remediation is possible.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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