dbcve.org
Contest GalleryWordPress extension

CVE-2024-32778

HIGH · 8.1 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 21.3.5 or later.
See remediation →
87/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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') 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 · moderate confidence

Path traversal vulnerability in the Contest Gallery WordPress plugin allows attackers to access files outside the intended directory through manipulation of file path inputs using '../' sequences. The vulnerability exists in versions through 21.3.4 and could allow unauthorized file access or disclosure.

MitigationUpdate Contest Gallery plugin to version 21.3.5 or later which contains the patched code. As a temporary measure, consider implementing WAF rules to block directory traversal patterns in requests.

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:< 21.3.5

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Identify if Contest Gallery plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Contest Gallery', or check the plugin files in /wp-content/plugins/contest-gallery/ for a main PHP file containing version metadata
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress adminPlugins list, locate Contest Gallery and read the version number under the plugin name, or inspect the main plugin PHP file for a 'Version:' header comment
    Affected if Version is 21.3.4 or lower (any version before 21.3.5)
  3. Check for file handling endpoints
    Inspect plugin directory /wp-content/plugins/contest-gallery/ for PHP files handling file uploads, downloads, or path parameters, particularly files with names suggesting file operations (upload, download, file, path, image, etc.)
    Affected if Plugin contains file handling code that processes user-supplied path inputs without sanitization
  4. Verify path traversal is exploitable
    Review identified file handling code for direct use of $_GET, $_POST, or $_REQUEST parameters in file operations (file_get_contents, include, require, fopen, etc.) without validation blocking '../' sequences
    Affected if Code accepts unvalidated path parameters and the plugin is accessible to unauthenticated users

User is affected if Contest Gallery plugin versions below 21.3.5 are installed and accessible, with file handling endpoints that process unvalidated path inputs.

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 21.3.5 or later
Fixed in 21.3.5
Interim mitigation

Update Contest Gallery plugin to version 21.3.5 or later which contains the patched code. As a temporary measure, consider implementing WAF rules to block directory traversal patterns in requests.

Recommended fix High confidence

Contest Gallery 21.3.5

  1. 1. Back up your WordPress site and database before performing any updates
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Find Contest Gallery in the plugin list and click 'Update Now' if an update is available
  4. 4. If automatic update is not available, download Contest Gallery version 21.3.5 or later from the WordPress plugin repository
  5. 5. Upload and install the new version through Plugins > Add New > Upload Plugin
  6. 6. Verify the plugin version is now 21.3.5 or later under Plugins > Installed Plugins
  7. 7. Test contest gallery functionality to ensure the update did not break expected features

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

Fix this in Contest Gallery Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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