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. |
| Impact | While the CVSS score of 6.5 (Medium) reflects a network-accessible vulnerability affecting confidentiality, integrity, and availability, several factors suggest lower real-world risk. The CVSS vector (AV:N/AC:L/PR:L/UI:R) indicates the attack requires low complexity but necessitates authenticated access (PR:L) and user interaction (UI:R), which significantly constrains opportunistic exploitation. The extremely low EPSS score of 0.03% (percentile 8%) demonstrates that empirical data indicates minimal actual exploitation probability. No public exploit code exists, and there is no CISA KEV confirmation of active exploitation. While the vulnerability affects WordPress plugins broadly deployed, the combination of authentication requirements, required user interaction, and negligible real-world exploitation signals suggests this is a lower-priority remediation compared to higher-EPSS unauthenticated remote code execution flaws. Organizations should prioritize this alongside regular plugin maintenance rather than as an emergency response. |
| Exploit ScenarioDerived | An authenticated WordPress user with low-level permissions (such as a contributor or subscriber if the plugin exposes input fields) crafts a malicious URL or posts content containing a DOM-based XSS payload targeting the Blog Filter plugin. When a site administrator or another user visits the compromised page or interacts with the crafted input, the malicious script executes in their browser context, potentially allowing the attacker to steal session cookies, perform unauthorized actions, or redirect the victim to a phishing site. The requirement for both authentication and user interaction limits the practical impact compared to worm-like unauthenticated XSS vulnerabilities. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 08, 2026
DOM-Based Cross-Site Scripting (XSS) in A WP Life Blog Filter WordPress plugin versions 1.7.6 and earlier allows authenticated attackers with low privileges to inject malicious scripts that execute in victims' browsers when they interact with crafted web pages. The vulnerability stems from improper neutralization of user input during page generation and requires user interaction to trigger. No public exploit code or active exploitation has been identified at the time of analysis, with an EPSS score of 0.03% indicating low exploitation probability.
RemediationAI
Update the A WP Life Blog Filter plugin to a version newer than 1.7.6 as soon as a patched release is made available. Website administrators should navigate to WordPress Dashboard > Plugins, locate Blog Filter, and apply the available update. Until a patch is released, users may temporarily disable or remove the plugin if its functionality is not critical. For additional details and updates, consult the advisory at https://patchstack.com/database/Wordpress/Plugin/blog-filter/vulnerability/wordpress-blog-filter-plugin-1-7-6-cross-site-scripting-xss-vulnerability?_s_id=cve and monitor the official plugin repository or vendor notifications for patch availability.
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
This vulnerability is a DOM-Based XSS flaw (CWE-79: Improper Neutralization of Input During Web Page Generation) in the A WP Life Blog Filter WordPress plugin, identified by CPE cpe:2.3:a:a_wp_life:blog_filter:*:*:*:*:*:*:*:*. DOM-Based XSS occurs when client-side JavaScript code processes user-controlled data without proper sanitization or encoding, allowing attackers to inject arbitrary scripts that execute in the document object model. Unlike reflected or stored XSS, DOM-based variants are particularly dangerous because the malicious payload may not appear in the HTML source and can be difficult to detect with server-side security tools. The plugin processes user input during web page generation without adequate output encoding or input validation, creating a pathway for script injection.
Know when Blog Filter 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:L/UI:R/S:C/C:L/I:L/A:L
Primary rating from Vendor (Patchstack) · only source for this CVE.
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in A WP Life Blog Filter blog-filter allows DOM-Based XSS.This issue affects Blog Filter: from n/a through <= 1.7.6.
Threat Intelligence Overview
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.
More in Blog Filter
View allThe Blog Filter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'AWL-BlogFilter' shortcode in vers
The Comments by Startbit plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'vivafbcomment' shortcode
EUVD-2026-20179
GHSA-fw58-q5m2-3fgm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB