dbcve.org
Contest GalleryWordPress extension

CVE-2024-24887

HIGH · 8.8 CVSS v3.1 Published 2024-02-12
Fix available
A fix is available. Upgrade to 21.2.9 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Contest Gallery Photos and Files Contest Gallery – Contact Form, Upload Form, Social Share and Voting Plugin for WordPress.This issue affects Photos and Files Contest Gallery – Contact Form, Upload Form, Social Share and Voting Plugin for WordPress: from n/a through 21.2.8.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

Cross-Site Request Forgery (CSRF) vulnerability in the Contest Gallery WordPress plugin allows attackers to trick authenticated users into performing unintended actions such as manipulating contest entries, votes, or file uploads. The vulnerability exists due to missing or improper CSRF token validation on plugin actions.

MitigationUpdate to the latest patched version of Contest Gallery when available. In the meantime, ensure WordPress users are educated about phishing threats and consider disabling the plugin if not essential.

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.2.9

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm Contest Gallery plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Contest Gallery' in the list of active plugins.
    Affected if The plugin is present and active in the WordPress installation
  2. Identify installed version number
    In the plugins list, find Contest Gallery and note the version number displayed beneath the plugin name. Alternatively, check the plugin header in wp-content/plugins/contest-gallery/index.php or readme.txt file.
    Affected if Version is lower than 21.2.9 (e.g., 21.2.8, 21.2.0, 20.x, etc.)
  3. Verify WordPress user authentication is enabled
    Check if WordPress user registration or any user accounts exist that can access the contest gallery functionality. Navigate to Users in WP admin to confirm active users.
    Affected if Any authenticated user accounts exist in WordPress (the CSRF affects actions performed by any logged-in user)
  4. Confirm plugin frontend functionality is accessible
    Visit the contest gallery page on the frontend of the website. Check if users can submit entries, votes, or file uploads through the gallery forms.
    Affected if Contest submission, voting, or upload forms are publicly accessible or available to logged-in users

You are affected if Contest Gallery plugin version is installed and is lower than 21.2.9, with active user accounts and accessible contest functionality.

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.2.9 or later
Fixed in 21.2.9
Interim mitigation

Update to the latest patched version of Contest Gallery when available. In the meantime, ensure WordPress users are educated about phishing threats and consider disabling the plugin if not essential.

Recommended fix High confidence

Contest Gallery version 21.2.9

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Contest Gallery plugin
  4. 4. Check if the current version is below 21.2.9
  5. 5. If an update is available, click 'Update Now' to upgrade to version 21.2.9
  6. 6. Verify the update was successful by checking the plugin version after completion
  7. 7. Test the plugin functionality to ensure the update did not break any 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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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