EUVD-2026-40274
GHSA-29c9-xrhx-266f
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running vulnerable plugin
-
DeliverySend request with script in taxonomy_include_children
-
ExploitPayload stored unsanitized
-
ExecutionVictim loads injected page
-
PersistScript executes in victim browser
-
ImpactSteal session or perform admin actions
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The target site must be running the Ajax Load More - Filters plugin at version 3.4.1 or earlier with filter functionality that processes the 'taxonomy_include_children' parameter. Per the CVSS vector (PR:N), injection requires no authentication; the limiting factor for impact is that the stored payload only fires when a user actually visits the injected page, and the confidentiality/integrity impact is rated Low (C:L/I:L), meaning consequences are scoped to the victim's browser context rather than direct server compromise. Realistic risk also depends on the unconfirmed assumption that the injecting request is truly unauthenticated - this should be validated against the Wordfence advisory. |
| Impact | The provided CVSS vector (AV:N/AC:L/PR:N/UI:N/S:C, C:L/I:L/A:N, score 7.2) indicates a network-reachable, low-complexity, unauthenticated stored XSS with a scope change - a genuinely meaningful issue for any internet-facing WordPress site running this add-on. However, several real-world risk signals are missing: no EPSS probability, no KEV listing, and no POC reference were supplied, so this is a high-CVSS finding without confirmed exploitation evidence. Stored XSS in WordPress plugins is frequently weaponized opportunistically, but the PR:N rating is unusually permissive for a parameter-based injection - verify with Wordfence whether the injecting request truly requires no authentication, as that materially changes priority. Treat as a real patch-soon priority for sites running the plugin, not a panic-grade emergency, pending exploitation telemetry. |
| Exploit ScenarioDerived | An attacker submits a crafted request that places a malicious value (for example an HTML/script payload) into the 'taxonomy_include_children' parameter, which the plugin stores and later renders unescaped on a filter-driven page. When a site administrator or visitor subsequently loads that page, the script executes in their browser session, enabling session/cookie theft, admin-action forgery, or redirection. No public POC is referenced, but the low attack complexity and network vector make exploitation straightforward to develop. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 30, 2026
Stored cross-site scripting in the Ajax Load More - Filters WordPress plugin (all versions through 3.4.1) lets unauthenticated attackers persist arbitrary JavaScript via the 'taxonomy_include_children' parameter, which then executes in the browser of any user who loads an affected page. Wordfence rates it CVSS 7.2 with a changed scope, reflecting that injected script runs in the context of other site visitors and administrators. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
RemediationAI
No vendor-released patch version is identified in the available data; affected versions are stated as all releases up to and including 3.4.1, so administrators should monitor https://ajaxloadmore.com/add-ons/filters/ and the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/6e8d9f73-8460-4bcb-a9f8-08eb058bcc09?source=cve) for a fixed release (expected to be the next version above 3.4.1) and upgrade immediately once published. Until a fix is available, deactivate the Filters add-on if the taxonomy-filter functionality is non-essential, which removes the vulnerable code path at the cost of losing dynamic filtering UI. As a compensating control, place a Web Application Firewall (such as Wordfence's) in front of the site to block requests containing script payloads in the 'taxonomy_include_children' parameter, accepting that WAF signatures may miss novel encodings, and restrict who can submit filter requests where feasible.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic CWE-79 (Improper Neutralization of Input During Web Page Generation) in a WordPress add-on. Ajax Load More - Filters extends the popular Ajax Load More plugin (vendor CPE connekt_media:ajax_load_more_-_filters) to build taxonomy/term-based filter UIs that fetch posts asynchronously. The 'taxonomy_include_children' parameter - normally a boolean controlling whether child terms of a taxonomy are included in a query - is reflected into generated page markup without sufficient input sanitization or output escaping, so attacker-controlled values are stored and later rendered as live HTML/JS rather than inert text.
Know when Ajax Load More Filters gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Network-reachable unauthenticated stored XSS (AV:N/AC:L/PR:N) with changed scope since script runs in other users' sessions; Low C/I and no availability impact match browser-context compromise.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The 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.
Articles & Coverage 1
Executive ViewAI
The Ajax Load More - Filters WordPress plugin (versions through 3.4.1) contains a stored cross-site scripting vulnerability that allows unauthenticated attackers to inject persistent malicious code affecting all site visitors and administrators. Organizations running WordPress sites with this plugin face potential account compromise, data exfiltration, and visitor exploitation since no vendor patch is currently available.
Disable the affected plugin until patch availability; implement WAF signature rules targeting the 'taxonomy_include_children' parameter injection vectors; deploy strict Content Security Policy (CSP) to restrict inline script execution; enable HTTP-only and secure flags on session cookies; conduct forensic audit of site logs for exploitation signs; restrict administrator account access to known locations/VPNs; monitor installed plugin version inventory continuously.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Exploit-DB