Contest GalleryWordPress extension
CVE-2022-45848
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. Stored Cross-Site Scripting (XSS) vulnerability in Contest Gallery plugin <= 13.1.0.9 on WordPress.
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 · high confidenceAn unauthenticated stored Cross-Site Scripting (XSS) vulnerability exists in the Contest Gallery WordPress plugin versions 13.1.0.9 and earlier. The vulnerability allows attackers to inject malicious JavaScript code that gets stored on the server and executed when other users view the affected content.
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
<= 13.1.0.9CVSS 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.
-
Verify Contest Gallery plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Contest Gallery' in the plugin list.Affected if Contest Gallery plugin appears in the installed plugins list
-
Check installed version numberIn the Plugins list, locate Contest Gallery and note the version number displayed beneath the plugin name. Alternatively, check the plugin file header in /wp-content/plugins/contest-gallery/ or view the plugin's main file.Affected if The version is 13.1.0.9 or any version lower than 13.1.0.9
-
Confirm plugin is activeIn the Plugins list, verify the Contest Gallery plugin shows as 'Active' (not deactivated).Affected if Plugin is active and version is 13.1.0.9 or earlier
-
Identify exposed user input endpointsReview the plugin settings to determine which features accept public user input (such as contest entries, voting forms, or gallery submissions). Since this is an unauthenticated XSS, check any publicly accessible submission forms.Affected if Public-facing submission or voting forms exist and the plugin version is 13.1.0.9 or earlier
If the Contest Gallery plugin is installed, active, and running version 13.1.0.9 or earlier, the environment is vulnerable to unauthenticated stored XSS via public input forms.
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 13.1.0.9, or apply proper input sanitization and output encoding to all user-supplied data before storage and rendering.
Fix this in Contest Gallery
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45848 — 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-2022-45848 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