Contest GalleryWordPress extension
CVE-2024-30238
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.2.
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 confidenceSQL injection vulnerability in Contest Gallery WordPress plugin (versions <=21.3.2) allows attackers to inject malicious SQL commands through unsanitized user inputs, potentially enabling unauthorized database access, data theft, or manipulation.
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.2.1CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the installed version of Contest GalleryAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, find Contest Gallery and read the version number from the plugin descriptionAffected if Version displayed is lower than 21.3.2.1 (for example 21.3.2, 21.3.1, or earlier)
-
Confirm plugin is activeIn the same plugins list, verify that Contest Gallery shows as Active (not Deactivated)Affected if The plugin is currently active and version is below 21.3.2.1
-
Check plugin files directly for version stringAccess the plugin directory via file manager or FTP, open the main plugin PHP file (usually named contest-gallery.php or similar) and locate the 'Version:' header comment in the plugin metadataAffected if The version number in the file header is below 21.3.2.1
A system is affected if Contest Gallery plugin is active and the installed version is any version prior to 21.3.2.1 (including 21.3.2 and all earlier versions).
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.2.1
Update Contest Gallery to the latest patched version when released. Until then, restrict access to affected plugin endpoints and implement input validation/parameterized queries at the application layer.
21.3.2.1
- 1. Back up your WordPress site and database before making any changes
- 2. Navigate to the WordPress admin dashboard > Plugins
- 3. Find Contest Gallery in the installed plugins list
- 4. Click 'Update now' if an update is available, or manually update to version 21.3.2.1 or later
- 5. Verify the update completed successfully
- 6. Test that the contest gallery functionality works as expected
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
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30238 — 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-30238 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