Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-1853: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in digiblogger BuddyHolis ListSearch

0
Medium
VulnerabilityCVE-2026-1853cvecve-2026-1853cwe-79
Published: Wed Feb 11 2026 (02/11/2026, 08:26:25 UTC)
Source: CVE Database V5
Vendor/Project: digiblogger
Product: BuddyHolis ListSearch

Description

The BuddyHolis ListSearch plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'listsearch' shortcode in all versions up to, and including, 1.1 due to insufficient input sanitization and output escaping on user supplied attributes. 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.

AI-Powered Analysis

AILast updated: 02/18/2026, 09:57:41 UTC

Technical Analysis

CVE-2026-1853 identifies a stored cross-site scripting vulnerability in the BuddyHolis ListSearch plugin for WordPress, present in all versions up to and including 1.1. The vulnerability arises from improper neutralization of input during web page generation, specifically insufficient sanitization and escaping of user-supplied attributes in the 'listsearch' shortcode. Authenticated users with contributor-level access or higher can exploit this flaw by injecting arbitrary JavaScript code into pages or posts. When other users visit these compromised pages, the malicious scripts execute within their browsers, potentially allowing attackers to hijack user sessions, steal cookies, perform actions on behalf of users, or escalate privileges. The vulnerability is classified under CWE-79 (Improper Neutralization of Input During Web Page Generation) and has a CVSS v3.1 base score of 6.4, reflecting medium severity. The attack vector is network-based with low attack complexity, requiring only privileges of a contributor or above, no user interaction, and impacts confidentiality and integrity but not availability. Although no known exploits have been reported in the wild, the vulnerability poses a significant risk to WordPress sites using this plugin, especially those with multiple contributors. The lack of a patch at the time of reporting necessitates interim mitigations such as restricting contributor privileges, monitoring for suspicious shortcode usage, or applying manual code fixes to sanitize inputs and escape outputs properly.

Potential Impact

For European organizations, the impact of this vulnerability can be significant, particularly for those relying on WordPress sites with multiple content contributors. Exploitation could lead to unauthorized disclosure of sensitive information, session hijacking, and unauthorized actions performed under the guise of legitimate users, undermining trust and potentially causing reputational damage. Organizations in sectors such as media, education, government, and e-commerce that use the BuddyHolis ListSearch plugin are at heightened risk. The vulnerability could facilitate further attacks like phishing or malware distribution by injecting malicious scripts into trusted websites. Given the medium severity, the impact is moderate but can escalate if combined with other vulnerabilities or social engineering tactics. The requirement for contributor-level access limits the attack surface but does not eliminate risk, especially in environments with many contributors or weak internal controls. Additionally, the cross-site scripting vulnerability can affect compliance with data protection regulations like GDPR if personal data is compromised.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Immediately audit WordPress sites to identify the presence of the BuddyHolis ListSearch plugin and verify the version in use. 2) Restrict contributor-level access to trusted personnel only and review user permissions regularly. 3) Monitor and log usage of the 'listsearch' shortcode to detect unusual or unauthorized script injections. 4) Until an official patch is released, consider disabling or removing the plugin if feasible. 5) Apply manual input validation and output escaping in the plugin code, focusing on sanitizing all user-supplied attributes in the shortcode. 6) Educate content contributors about the risks of injecting untrusted content and enforce secure content creation policies. 7) Employ web application firewalls (WAFs) with rules to detect and block common XSS payloads targeting this plugin. 8) Keep WordPress core and all plugins updated to minimize exposure to other vulnerabilities. 9) Conduct regular security assessments and penetration testing focusing on content management systems. 10) Prepare incident response plans to quickly address any exploitation attempts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-02-03T18:32:47.519Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 698c3e564b57a58fa1832d9a

Added to database: 2/11/2026, 8:31:18 AM

Last enriched: 2/18/2026, 9:57:41 AM

Last updated: 2/21/2026, 12:18:20 AM

Views: 26

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats