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-13857: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in ksakai Yet Another WebClap for WordPress

0
Medium
VulnerabilityCVE-2025-13857cvecve-2025-13857cwe-79
Published: Sat Dec 06 2025 (12/06/2025, 05:49:34 UTC)
Source: CVE Database V5
Vendor/Project: ksakai
Product: Yet Another WebClap for WordPress

Description

The Yet Another WebClap for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'text' parameter of the webclap_button shortcode in all versions up to, and including, 0.2 due to insufficient input sanitization and output escaping. 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/13/2025, 07:07:32 UTC

Technical Analysis

The vulnerability identified as CVE-2025-13857 affects the Yet Another WebClap plugin for WordPress, specifically all versions up to and including 0.2. It is a stored Cross-Site Scripting (XSS) vulnerability classified under CWE-79, caused by improper neutralization of input during web page generation. The flaw exists in the 'text' parameter of the webclap_button shortcode, where insufficient input sanitization and output escaping allow authenticated users with Contributor-level permissions or higher to inject arbitrary JavaScript code. When other users access the compromised page, the malicious script executes in their browsers, potentially leading to session hijacking, unauthorized actions, or data theft. The vulnerability requires no user interaction beyond page access but does require authenticated access with contributor or higher privileges, which limits the attack surface to some extent. The CVSS 3.1 base score is 6.4, indicating a medium severity with network attack vector, low attack complexity, and partial impact on confidentiality and integrity but no impact on availability. No patches or fixes are currently available, and no known exploits have been observed in the wild. The vulnerability is significant because WordPress is widely used across Europe, and many organizations rely on plugins like Yet Another WebClap for user engagement features. Attackers could leverage this vulnerability to compromise site visitors or administrators, potentially leading to broader compromise or reputational damage.

Potential Impact

For European organizations, the impact of this vulnerability can be substantial, particularly for those operating WordPress-based websites with multiple contributors or editors. Exploitation could allow malicious insiders or compromised contributor accounts to inject persistent malicious scripts, affecting all users who visit the infected pages. This can lead to theft of session cookies, redirection to phishing sites, or execution of unauthorized actions under the victim's credentials. Confidentiality and integrity of user data and site content are at risk, potentially undermining trust and compliance with data protection regulations such as GDPR. Although availability is not directly impacted, the reputational damage and potential regulatory consequences could be severe. Organizations in sectors with high web presence, such as media, e-commerce, and public services, are particularly vulnerable. The requirement for authenticated access somewhat limits the threat to insider or compromised accounts, but this does not eliminate risk given the prevalence of contributor roles in collaborative environments.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should immediately audit their WordPress installations to identify the presence of the Yet Another WebClap plugin, especially versions up to 0.2. If found, the plugin should be disabled or removed until a secure update is released. In the absence of an official patch, organizations can implement manual input validation and output escaping for the 'text' parameter in the shortcode, possibly by customizing the plugin code or using security plugins that enforce content sanitization. Restrict contributor-level permissions to trusted users only and monitor user-generated content for suspicious scripts. Employ Web Application Firewalls (WAFs) with rules targeting XSS payloads to provide an additional layer of defense. Regularly review user roles and permissions to minimize the risk of insider threats. Additionally, educate contributors about the risks of injecting untrusted content and implement logging and alerting for unusual shortcode usage or content changes. Finally, maintain up-to-date backups to enable quick recovery if exploitation occurs.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-01T20:31:53.275Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6933c71e11163305efef3deb

Added to database: 12/6/2025, 6:03:10 AM

Last enriched: 12/13/2025, 7:07:32 AM

Last updated: 2/4/2026, 7:21:04 AM

Views: 36

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