dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-8837

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The WP Iframe Geo Style for Amazon affiliates plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'adid' Shortcode Attribute in all versions up to, and including, 1.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 confidence

The WP Iframe Geo Style for Amazon affiliates plugin for WordPress fails to sanitize the 'adid' shortcode attribute input and escape output, allowing authenticated users with contributor-level permissions or higher to inject persistent malicious JavaScript that executes whenever pages containing the injected shortcode are accessed.

MitigationUpdate to a patched version when available; until then, audit user permissions, review existing posts/pages for malicious shortcode injections, and consider temporarily restricting contributor-level access.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WP Iframe Geo Style for Amazon affiliates' or search for 'iframe-geo-style' in the plugins directory
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    In Plugins list, click on the plugin name to view details, or check the plugin header in /wp-content/plugins/iframe-geo-style/iframe-geo-style.php for the 'Version' defined constant
    Affected if Version is unknown or falls within an unpatched range; compare against any official security advisory
  3. Audit user accounts with contributor-level or higher access
    Go to Users > All Users in WordPress admin and filter by role; examine any users with 'Contributor', 'Author', 'Editor', or 'Administrator' roles
    Affected if There are users with contributor-level permissions who could inject the malicious shortcode
  4. Search posts and pages for the vulnerable shortcode
    Use WP admin search or query the wp_posts table in MySQL for the string 'adid=' within shortcode brackets, e.g., SELECT * FROM wp_posts WHERE post_content LIKE '%[iframe_geo%adid=%'
    Affected if Any post/page contains a shortcode using the adid attribute with unsanitized content
  5. Inspect shortcode output for unescaped content
    View the source HTML of a page containing the shortcode; check if the adid value appears as raw HTML/JS without proper encoding (e.g., appears as <script> or event handler like onload=)
    Affected if The adid value renders as executable HTML or JavaScript rather than as escaped text
  6. Review recent activity logs for suspicious shortcode edits
    Check WordPress revision history or security logs for recent edits to posts containing the iframe_geo shortcode, looking for unusual adid values
    Affected if Shortcodes were recently added or modified with unusual adid parameter values

You are affected if the plugin is installed, there are contributor-level users, and any post contains the adid shortcode attribute with potentially unescaped content that could execute malicious JavaScript.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version when available; until then, audit user permissions, review existing posts/pages for malicious shortcode injections, and consider temporarily restricting contributor-level access.

Recommended fix Moderate confidence

latest available version (verify on wordpress.org/plugins)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'WP Iframe Geo Style for Amazon affiliates' plugin
  4. 4. Check if an update is available and update to the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8837 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8837 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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