CVE-2026-8698
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 Cryptocurrency Prijsvergelijking Widget plugin for WordPress is vulnerable to Stored Cross-Site Scripting in version 1.0. This is due to insufficient output escaping in the as_get_coin_shortcode() function, which renders the 'width' (and 'height') shortcode attribute directly into the style attribute of an <iframe> element without applying any escaping function such as esc_attr(). An attacker-controlled value like '100px;"onload="alert(1)" x="' terminates the style attribute prematurely and injects an arbitrary HTML attribute into the iframe tag. 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 Cryptocurrency Prijsvergelijking Widget plugin for WordPress fails to escape the 'width' and 'height' shortcode attributes in the as_get_coin_shortcode() function, rendering them directly into an iframe's style attribute without sanitization. Attackers with contributor-level access can inject malicious attribute values like '100px;"onload="alert(1)" x="' to achieve stored XSS execution.
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.
-
Identify if the plugin is installedNavigate to WordPress Admin > Plugins and look for 'Cryptocurrency Prijsvergelijking Widget' in the installed plugins listAffected if The plugin is not installed in WordPress
-
Check the plugin versionClick on the plugin in the Plugins list to view its version details, then compare against any known vulnerable version numbersAffected if The installed version is older than the patched version
-
Locate the vulnerable functionAccess the plugin files via FTP or File Manager, navigate to the plugin directory, and search for the function 'as_get_coin_shortcode' in PHP filesAffected if The function exists and contains iframe output with width/height attributes
-
Inspect pages using the shortcodeSearch post content for the shortcode (typically [coin] or similar) that accepts width and height attributes, then view the page source to inspect the rendered iframe HTMLAffected if The iframe style attribute contains raw, unescaped width/height values that could contain quotes or JavaScript payloads
-
Check for contributor-level usersGo to Users > All Users in WordPress admin and review user roles; contributor role or higher can exploit this vulnerabilityAffected if At least one user with contributor-level or higher access exists who could inject malicious shortcode content
A user is affected if the Cryptocurrency Prijsvergelijking Widget plugin is installed, contains the unpatched as_get_coin_shortcode function, and outputs iframe HTML with unsanitized width/height attributes in the style tag.
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 dataApply esc_attr() or equivalent escaping functions to the width and height parameter values before embedding them into the iframe HTML output.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8698 — 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-8698 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