CVE-2026-42680
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 · uneditedIncorrect Privilege Assignment vulnerability in Wasiliy Strecker / ContestGallery developer Contest Gallery Pro allows Privilege Escalation. This issue affects Contest Gallery Pro: from n/a through 29.0.1.
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 confidenceA privilege escalation vulnerability in the Contest Gallery Pro WordPress plugin allows attackers to gain higher-level permissions due to incorrect privilege assignment. The issue stems from improper capability checks that permit lower-privileged users (such as subscribers) to perform administrative actions or access functionality they should not have access to.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Contest Gallery Pro plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Contest Gallery Pro' or check the wp-content/plugins/ folder for contest-gallery-pro directoryAffected if The plugin is present in the WordPress installation
-
Check installed plugin versionIn WordPress admin > Plugins, find Contest Gallery Pro and note the version number displayed; alternatively, check the main plugin PHP file for version constant or readme.txtAffected if Version is 29.0.1 or lower (vulnerable versions before the patch)
-
Review user roles for unexpected privilege escalationIn WordPress admin > Users, examine all user accounts for roles beyond what they should have (e.g., standard users with Administrator role, or custom roles created by the plugin with elevated permissions)Affected if Any user has Administrator role or elevated privileges that were not assigned by a legitimate administrator
-
Inspect plugin role/permission configurationCheck Contest Gallery Pro settings pages in WordPress admin for any user role management, permission assignment, or 'user level' configuration options; look for options that allow role modificationAffected if Plugin settings allow modifying user roles or assigning new capabilities to lower-privileged users
-
Check for unauthorized admin accountsQuery the wp_usermeta table (via phpMyAdmin or WP-CLI 'wp user list') for newly created Administrator accounts, especially created recently or by user IDs that did not previously have admin accessAffected if New Administrator-level accounts exist that were not intentionally created
Environment is affected if Contest Gallery Pro plugin version 29.0.1 or lower is installed AND any user has privileges beyond what was intentionally assigned, indicating the privilege escalation flaw is present.
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 Contest Gallery Pro to the latest version immediately. Until then, restrict plugin access to trusted administrator accounts only and monitor for unauthorized administrative actions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42680 — 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-2026-42680 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