dbcve.org
Contest GalleryWordPress extension

CVE-2024-39631

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to 23.1.3 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Wasiliy Strecker / ContestGallery developer Contest Gallery contest-gallery.This issue affects Contest Gallery: from n/a through <= 23.1.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 confidence

A stored Cross-site Scripting (XSS) vulnerability in the Contest Gallery WordPress plugin allows attackers to inject malicious JavaScript through unsanitized user input fields. The injected payload executes in the browsers of other users who view the affected contest pages or admin interfaces.

MitigationUpdate to the latest patched version of Contest Gallery. Until patched, review and sanitize all user input fields and implement output encoding when displaying contest data in the browser.

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

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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
    Navigate to WordPress admin dashboard > Plugins and look for 'Contest Gallery' in the list of installed plugins
    Affected if Contest Gallery plugin is present and active in WordPress
  2. Identify installed version of Contest Gallery
    In WordPress admin > Plugins > Contest Gallery, view the plugin details to see the installed version number
    Affected if The installed version is lower than 23.1.3 (e.g., 23.1.2, 23.0.x, 22.x, etc.)
  3. Check for existing contests created with the plugin
    In WordPress admin, navigate to Contest Gallery section and review any contests that have been created
    Affected if Any contest entries exist in the system
  4. Verify contest visibility settings
    Examine the contest configuration to determine if contests are set to be visible to other users or publicly accessible
    Affected if Contests are publicly visible or accessible to users other than the creator

A user is affected if Contest Gallery version is below 23.1.3 AND there are contest entries created with user input fields that are visible to other users or administrators

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

Update to the latest patched version of Contest Gallery. Until patched, review and sanitize all user input fields and implement output encoding when displaying contest data in the browser.

Recommended fix High confidence

Contest Gallery 23.1.3

  1. 1. Create a complete backup of your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find Contest Gallery in the plugin list
  4. 4. Click 'Update now' if an update is available, or manually upload version 23.1.3 of Contest Gallery
  5. 5. Verify the plugin updated successfully by checking the version number in the plugins list
  6. 6. Test the Contest Gallery functionality to ensure the update did not break existing 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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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