CVE-2026-5505
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 WP-Clippy plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `clippy` shortcode in all versions up to, and including, 1.0.0. This is due to insufficient input sanitization and output escaping on user supplied attributes. 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 WP-Clippy WordPress plugin has a stored XSS vulnerability in its clippy shortcode (versions up to 1.0.0). Authenticated users with contributor-level access can inject arbitrary JavaScript via unsanitized shortcode attributes, which executes when other users view the compromised page.
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 WP-Clippy plugin is installedCheck your WordPress plugins directory or go to Plugins > Installed Plugins and look for WP-Cloppry or WP-Clippy in the listAffected if The plugin appears in the installed plugins list
-
Determine installed version of WP-ClippyOn the Plugins page, click on the plugin to view details, or check the plugin header comment in wp-content/plugins/wp-clippy/wp-clippy.php for the Version: lineAffected if The version is 1.0.0 or any version below 1.0.1
-
Identify contributor-level user accountsNavigate to Users > All Users in the WordPress admin and look for any users with the Contributor roleAffected if At least one user with Contributor role exists and has the ability to create or edit posts containing shortcodes
-
Search for clippy shortcode usage in contentUse WordPress search or query the wp_posts table for content containing the string [clippy] or [clippy_Affected if Any post, page, or custom post type contains a clippy shortcode that could have unsanitized attributes
You are affected if the WP-Clippy plugin is installed at version 1.0.0 or below AND at least one Contributor-level user exists AND clippy shortcodes are in use on your site.
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.
dbcve · scopedUpdate the plugin to version 1.0.1 or later which includes proper input sanitization and output escaping. Until patched, restrict contributor-level user creation and review existing shortcode usage.
latest version available in WordPress plugin repository (version > 1.0.0)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the WP-Clippy plugin in the list
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
- 6. After updating, verify the clippy shortcode still functions correctly on the site
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2026-5505 — 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-5505 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