Contest GalleryWordPress extension
CVE-2023-28784
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Contest Gallery plugin <= 21.1.2 versions.
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 confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in the Contest Gallery WordPress plugin affecting versions 21.1.2 and below. The vulnerability allows attackers to inject malicious scripts via unsanitized input, likely through URL parameters, which are reflected back to users without proper output encoding.
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.1.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Contest Gallery plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Contest Gallery' in the list. Alternatively, check the /wp-content/plugins/contest-gallery directory exists.Affected if Contest Gallery plugin is installed and active
-
Identify installed versionIn WordPress admin, go to Plugins > Installed Plugins, find Contest Gallery, and note the version number displayed. Alternatively, check the version in the plugin's main PHP file header or style.css.Affected if Version is 21.1.2 or lower
-
Determine if vulnerable endpoint is accessibleThe vulnerability is an unauthenticated reflected XSS via URL parameters. Check if the Contest Gallery plugin handles any front-end requests by visiting the site and attempting to access any Contest Gallery shortcodes or endpoints (often found at URLs containing '/contest-gallery/' or similar).Affected if Any Contest Gallery functionality is publicly accessible without authentication
-
Inspect for unsanitized URL reflectionTest by using a known-safe browser or intercepting tool to request a Contest Gallery URL with a test parameter (e.g., ?test=<script>alert(1)</script>) and observe if the parameter value is reflected in the response without encoding.Affected if URL parameters are reflected in the page output without proper HTML encoding
You are affected if the Contest Gallery plugin is installed at version 21.1.2 or below and any of its public-facing endpoints handle URL parameters that are reflected in the response.
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.
From vendor dataUpdate the Contest Gallery plugin to a version newer than 21.1.2 that contains the security patch, or implement proper input validation and output escaping on the vulnerable endpoint.
Fix this in Contest Gallery
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-28784 — 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-2023-28784 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