Contest GalleryWordPress extension
CVE-2024-30236
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Wasiliy Strecker / ContestGallery developer Contest Gallery contest-gallery.This issue affects Contest Gallery: from n/a through <= 21.3.4.
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 confidenceSQL injection vulnerability in the Contest Gallery WordPress plugin allows attackers to inject malicious SQL commands through unsanitized input parameters. The vulnerability affects all versions through 21.3.4 and can be exploited without authentication due to the improper neutralization of special elements in SQL queries.
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
< 21.3.5CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Contest Gallery and view the version number displayed, or check the plugin header in wp-content/plugins/contest-gallery/readme.txt or the main plugin file for the 'Version' headerAffected if Version listed is lower than 21.3.5 (e.g., 21.3.4, 21.3.3, etc.)
-
Verify plugin is activeConfirm the Contest Gallery plugin is activated in WordPress under Plugins > Installed Plugins. An inactive plugin may not expose the vulnerable code paths.Affected if Plugin status shows 'Active' and version is below 21.3.5
-
Confirm WordPress is serving the vulnerable codeIf possible, compare the contest-gallery main PHP file or SQL-handling files against the publicly available changelog for version 21.3.5 to see if the SQL sanitization fix is present in your installed copyAffected if Your installed files predate the 21.3.5 security release and no manual patches have been applied
Your environment is affected if the Contest Gallery plugin is active and the installed version is any version below 21.3.5, as this enables unauthenticated SQL injection through unsanitized input parameters.
Generated from the published advisory. Verify against your own configuration.
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 · scoped21.3.5
Update Contest Gallery plugin to the latest version (beyond 21.3.4) which contains the fix for this SQL injection vulnerability.
Contest Gallery 21.3.5 or latest available version
- Backup your WordPress site before making any changes
- Update the Contest Gallery plugin to version 21.3.5 or the latest available version through WordPress admin Dashboard > Plugins > Updates
- After updating, verify the plugin version reflects 21.3.5 or later in Plugins > Installed Plugins
- Clear any caching layers if applicable to ensure the patched code is served
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Contest Gallery
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30236 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-30236 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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