Contest GalleryWordPress extension

CVE-2024-30428

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to 24.0.4 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 allows Reflected XSS.This issue affects Contest Gallery: from n/a through <= 24.0.3.

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

Reflected XSS vulnerability in the Contest Gallery WordPress plugin allows unauthenticated attackers to inject malicious JavaScript code via unsanitized user input that gets reflected in web pages without proper output encoding.

MitigationFix requires implementing proper input validation and context-aware output encoding on all user-supplied parameters throughout the plugin, particularly in pages handling contest submissions and gallery displays.

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

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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Contest Gallery', or check if the /wp-content/plugins/contest-gallery/ directory exists on the server
    Affected if The plugin is present and active in the WordPress installation
  2. Identify installed version
    In WordPress admin, view the plugin details from the Plugins list to see the version number, or open the main plugin PHP file and check the 'Version' header in the plugin comment block
    Affected if The installed version is lower than 24.0.4 (for example, 24.0.3, 24.0.2, or earlier)
  3. Verify contest submission pages are accessible
    Visit pages on the site that contain contest submission forms or gallery displays. These are the areas where user input gets reflected. Check the frontend for any publicly accessible contest or gallery pages
    Affected if Publicly accessible contest submission or gallery display pages exist that accept user input
  4. Review access logs for XSS indicators
    Examine web server access logs (Apache, Nginx) or WordPress audit logs for unusual request parameters containing script tags, javascript:, or event handlers (onload, onerror, onclick) in URLs pointing to contest or gallery pages
    Affected if Log entries show attempts to inject malicious script content via URL parameters on contest/gallery pages

The environment is affected if the Contest Gallery plugin is installed with a version lower than 24.0.4 and publicly accessible contest submission or gallery pages exist that could reflect unsanitized user input.

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

Fix requires implementing proper input validation and context-aware output encoding on all user-supplied parameters throughout the plugin, particularly in pages handling contest submissions and gallery displays.

Recommended fix High confidence

24.0.4

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin
  3. Locate Contest Gallery in the plugin list
  4. Check if an update is available (look for version 24.0.4 or higher)
  5. If an update is available, click 'Update Now' to install version 24.0.4
  6. Verify the update completed successfully by checking the plugin version
  7. Test the plugin functionality to ensure it operates correctly after the update

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
17.0 hours of engineering $3,000
Get the upgrade done

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 locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-30428 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