CVE-2026-8141
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 Ajax Load More - Filters plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'taxonomy_include_children' parameter in all versions up to, and including, 3.4.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers 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 Ajax Load More - Filters WordPress plugin fails to sanitize the 'taxonomy_include_children' parameter during input and does not escape it during output, allowing stored XSS. Unauthenticated attackers can inject malicious scripts via this parameter that execute when users view affected pages.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 Ajax Load More - Filters plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Ajax Load More - Filters' in the list. Alternatively, check the /wp-content/plugins/ajax-load-more-filters/ directory exists on the server.Affected if Plugin is installed and active
-
Check installed plugin versionIn WordPress admin Plugins page, find Ajax Load More - Filters and view the version number displayed beneath the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/ajax-load-more-filters/ for the Version field.Affected if Version is lower than 3.4.2
-
Identify if taxonomy_include_children parameter is in useSearch your WordPress site for pages, posts, or custom post types that use Ajax Load More filters with taxonomy queries. Check the plugin settings or shortcode implementations for taxonomy_include_children parameter usage.Affected if The parameter is being used in any query or filter configuration
-
Inspect for injected malicious scriptsReview page source of affected pages for unexpected script tags, iframe elements, or inline JavaScript in the taxonomy_include_children output area. Check database wp_postmeta or relevant custom tables for unusual script content in filter values.Affected if Suspicious scripts are present in page output or database entries for taxonomy filter parameters
Environment is affected if Ajax Load More - Filters plugin version is below 3.4.2 and the taxonomy_include_children parameter is exposed or being used 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 dataUpdate the plugin to version 3.4.2 or later which includes proper input sanitization and output escaping for the taxonomy_include_children parameter. If immediate update is not possible, consider disabling the plugin until the patch can be applied.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8141 — 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-8141 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