CVE-2026-8703
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 Endless Scroll plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Shortcode Attributes in all versions up to, and including, 1.0.0 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 Endless Scroll WordPress plugin up to version 1.0.0 contains a stored XSS vulnerability in its shortcode handler. Authenticated users with contributor-level permissions can inject malicious JavaScript via shortcode attributes due to missing input sanitization and output escaping, causing scripts to execute whenever affected pages are accessed.
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 Endless Scroll plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Endless Scroll' in the list. Note the version number displayed.Affected if The plugin is installed and shows version 1.0.0 or lower
-
Confirm shortcode usage on the siteSearch posts, pages, and widget content for the string '[endless_scroll' using WordPress admin search or by querying the wp_posts database table for this shortcode pattern.Affected if The shortcode [endless_scroll] appears in any published content on the site
-
Identify users with contributor-level accessNavigate to Users > All Users in WordPress admin and review the role column. Users with Contributor, Author, Editor, or Administrator roles can exploit this vulnerability.Affected if At least one user account has Contributor role or higher AND the plugin version is 1.0.0 or below
-
Inspect plugin shortcode handler for sanitizationLocate the plugin file containing the shortcode callback (typically in the main plugin PHP file). Search for the function registering [endless_scroll] and examine how it handles attributes - look for absence of sanitize_text_field(), esc_attr(), esc_html(), or esc_js().Affected if Shortcode attributes are processed without input sanitization functions or output escaping functions, and the plugin version is 1.0.0 or below
A site is affected if the Endless Scroll plugin version 1.0.0 or lower is installed, the shortcode is in use, and any user with Contributor-level permissions or higher exists on the 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.
From vendor dataUpgrade to version 1.0.1 or later, or apply sanitization (esc_attr(), sanitize_text_field()) to shortcode attribute inputs and output escaping (esc_html(), esc_js()) before rendering.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8703 — 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-8703 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