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-2025-13884: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in buntegiraffe Hide Email Address

0
Medium
VulnerabilityCVE-2025-13884cvecve-2025-13884cwe-79
Published: Fri Dec 12 2025 (12/12/2025, 03:20:52 UTC)
Source: CVE Database V5
Vendor/Project: buntegiraffe
Product: Hide Email Address

Description

The Hide Email Address plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'inline_css' parameter in the `bg-hide-email-address` shortcode in all versions up to, and including, 0.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: 12/12/2025, 04:12:00 UTC

Technical Analysis

CVE-2025-13884 identifies a stored cross-site scripting vulnerability in the 'Hide Email Address' WordPress plugin developed by buntegiraffe. The flaw exists in the handling of the 'inline_css' parameter within the 'bg-hide-email-address' shortcode, where insufficient input sanitization and output escaping allow malicious scripts to be injected and stored persistently in the website content. Authenticated users with Contributor-level permissions or higher can exploit this vulnerability by submitting crafted input that embeds arbitrary JavaScript code. When any user visits the affected page, the malicious script executes in their browser context, potentially compromising user sessions, stealing cookies, or performing unauthorized actions on behalf of the user. The vulnerability affects all versions up to and including 0.1 of the plugin. The CVSS v3.1 base score is 6.4, reflecting a medium severity with network attack vector, low attack complexity, privileges required, no user interaction, and a scope change. Although no public exploits are currently known, the vulnerability's presence in a widely used CMS plugin makes it a significant risk. The lack of patches or official fixes at the time of publication necessitates immediate attention from site administrators. The vulnerability is particularly concerning because Contributor-level users are often legitimate content creators, making insider threat or compromised accounts a plausible attack vector. The stored nature of the XSS means that the malicious payload persists and affects all visitors to the infected page, increasing the potential impact.

Potential Impact

For European organizations, this vulnerability poses a risk to the confidentiality and integrity of web applications running WordPress with the affected plugin. Attackers exploiting this flaw can hijack user sessions, steal sensitive information such as authentication tokens, or manipulate site content, potentially leading to reputational damage, data breaches, and unauthorized access. Since Contributor-level users can exploit the vulnerability, insider threats or compromised accounts increase the risk. The persistent nature of the XSS means that all visitors to the infected pages are at risk, including customers and employees, which could lead to widespread compromise. Organizations in sectors with high regulatory requirements for data protection, such as finance, healthcare, and government, may face compliance violations if exploited. Additionally, the vulnerability could be leveraged to distribute malware or phishing content, amplifying its impact. The medium CVSS score indicates a moderate but actionable threat that should not be ignored, especially given the popularity of WordPress in Europe.

Mitigation Recommendations

European organizations should immediately audit their WordPress sites for the presence of the 'Hide Email Address' plugin by buntegiraffe and verify the version in use. Since no official patches are currently available, temporary mitigations include disabling or removing the plugin until a fix is released. Restrict Contributor-level user permissions by enforcing stricter access controls and monitoring user activity for suspicious behavior. Implement web application firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the 'inline_css' parameter in the shortcode. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers. Conduct regular security reviews and scanning for stored XSS vulnerabilities using automated tools. Educate content contributors about the risks of injecting untrusted input and enforce input validation policies. Monitor logs for unusual activity related to shortcode usage or user-generated content modifications. Once a patch is released, prioritize its deployment across all affected systems.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-02T14:34:47.305Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693b9185650da22753edbccf

Added to database: 12/12/2025, 3:52:37 AM

Last enriched: 12/12/2025, 4:12:00 AM

Last updated: 12/13/2025, 10:40:43 PM

Views: 11

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats