CVE-2026-8607
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 · uneditedThe Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program – myCred plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'wrap' Shortcode Attribute in all versions up to, and including, 3.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 confidenceThe myCred WordPress plugin versions up to 3.1 contain a stored XSS vulnerability in the shortcode handler for the 'wrap' attribute. Authenticated users with contributor-level permissions can inject malicious JavaScript through the shortcode, which persists in the database and executes when other users view affected pages due to missing input sanitization and output escaping.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 myCred plugin is installedNavigate to WordPress admin > Plugins and locate myCred, or check the plugin files for version information in the main plugin file headerAffected if myCred plugin is present in the WordPress installation
-
Determine installed myCred versionIn WordPress admin > Plugins, view the myCred plugin details to see the version number, or inspect the main plugin file for the 'Version' header commentAffected if Version is 3.1 or lower (versions 3.2 and later contain the fix)
-
Identify use of myCred wrap shortcodeSearch WordPress database posts (wp_posts table) for the shortcode pattern '[mycred_wrap' or '[mycred_mycred_wrap' in post_content column, or use WordPress search functionality to find pages using this shortcodeAffected if The 'wrap' shortcode is used in any published post or page content
-
Inspect shortcode attributes for unsanitized contentExamine the wrap shortcode instances in post content, specifically looking at the 'wrap' attribute value - check if it contains quotes, angle brackets, or JavaScript-like patternsAffected if The wrap attribute contains unescaped HTML characters, quotes, or suspicious patterns that suggest injection attempts
You are affected if myCred version is 3.1 or lower AND the wrap shortcode is used in your content with unsanitized user-supplied values in the wrap attribute.
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 myCred plugin to version 3.2 or later which includes proper sanitization of the 'wrap' shortcode parameter and output escaping. Alternatively, restrict shortcode usage to administrator-level users until the patch is applied.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8607 — 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-8607 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