dbcve.org
Contest GalleryWordPress extension

CVE-2025-22693

HIGH · 7.2 CVSS v3.1 Published 2025-02-03
Fix available
A fix is available. Upgrade to 25.1.2 or later.
See remediation →
78/100
Remediation priority · High
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 Wasiliy Strecker / ContestGallery developer Contest Gallery contest-gallery allows SQL Injection.This issue affects Contest Gallery: from n/a through <= 25.1.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

SQL Injection vulnerability in the Contest Gallery WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user inputs. The vulnerability stems from improper neutralization of special elements in SQL queries, potentially allowing unauthorized database access, data exfiltration, or manipulation.

MitigationUpdate Contest Gallery plugin to the latest version once a patch is released. If no patch is available, temporarily disable the plugin or implement web application firewall rules to block SQL injection attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Contest GalleryWordPress extension
Affected:< 25.1.2

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

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

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
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Contest Gallery' in the list, or inspect the /wp-content/plugins/contest-gallery directory via file system
    Affected if Contest Gallery plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin > Plugins, find Contest Gallery and view the version number under the plugin name, or read the 'Version' field from the plugin's main PHP file header in /wp-content/plugins/contest-gallery/
    Affected if Version is lower than 25.1.2 (for example, 25.1.0, 24.5.3, etc.)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the Contest Gallery plugin shows 'Active' status rather than 'Inactive'
    Affected if Plugin is active and processing user inputs through its forms or contest submissions
  4. Identify attack surface for SQL injection
    Review plugin settings and frontend contest forms to see which user input fields accept and store user data (such as name, email, entry content, or custom fields) that could be passed to SQL queries
    Affected if Plugin accepts user-submitted data through forms without visible sanitization and stores it in the database

You are affected if Contest Gallery plugin version is below 25.1.2 and the plugin is active with user input forms enabled.

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
Upgrade available Upgrade to 25.1.2 or later
Fixed in 25.1.2
Interim mitigation

Update Contest Gallery plugin to the latest version once a patch is released. If no patch is available, temporarily disable the plugin or implement web application firewall rules to block SQL injection attempts.

Recommended fix High confidence

Contest Gallery 25.1.2

  1. Backup your WordPress site and database before making any changes
  2. Update the Contest Gallery plugin to version 25.1.2 or later through the WordPress admin dashboard or via FTP
  3. Verify the update was successful by checking the plugin version in WordPress admin > Plugins
  4. Test that Contest Gallery functionality works as expected after the update

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

Fix this in Contest Gallery Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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