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-13729: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in greenshady Entry Views

0
Medium
VulnerabilityCVE-2025-13729cvecve-2025-13729cwe-79
Published: Fri Jan 09 2026 (01/09/2026, 09:19:46 UTC)
Source: CVE Database V5
Vendor/Project: greenshady
Product: Entry Views

Description

The Entry Views plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'entry-views' shortcode in all versions up to, and including, 1.0.0 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

Machine-generated threat intelligence

AILast updated: 02/27/2026, 10:14:39 UTC

Technical Analysis

CVE-2025-13729 is a stored Cross-Site Scripting (XSS) vulnerability identified in the Entry Views plugin for WordPress, developed by greenshady. The vulnerability arises from improper neutralization of input during web page generation (CWE-79), specifically due to insufficient sanitization and output escaping of user-supplied attributes in the plugin's 'entry-views' shortcode. This flaw affects all versions up to and including 1.0.0. An attacker with authenticated access at the contributor level or higher can inject arbitrary JavaScript code into pages by manipulating shortcode attributes. Because the malicious script is stored and rendered whenever the page is accessed, it can execute in the context of any user visiting the page, potentially leading to session hijacking, privilege escalation, or unauthorized actions on behalf of the victim. The vulnerability has a CVSS 3.1 base score of 6.4, indicating medium severity, with an attack vector of network, low attack complexity, requiring privileges (PR:L), no user interaction, and scope change (S:C). No public exploits have been reported yet. The vulnerability was reserved in late 2025 and published in early 2026. The plugin's widespread use in WordPress sites and the common presence of contributor-level users increase the risk of exploitation if unpatched.

Potential Impact

The primary impact of this vulnerability is the compromise of confidentiality and integrity of user sessions and data on affected WordPress sites. Exploitation allows attackers to execute arbitrary scripts in the browsers of site visitors, which can lead to theft of authentication cookies, defacement, or redirection to malicious sites. Since the vulnerability requires contributor-level access, attackers must first gain some level of authenticated access, which is common in collaborative content management environments. The scope change in the CVSS vector indicates that the vulnerability can affect resources beyond the initially compromised component, potentially impacting the entire site or user base. Although availability is not directly affected, the reputational damage and potential data breaches can have significant operational and financial consequences for organizations. The absence of known exploits in the wild suggests a window for proactive mitigation before widespread attacks occur.

Mitigation Recommendations

1. Immediately update the Entry Views plugin to a patched version once available from the vendor or disable the plugin if an update is not yet released. 2. Restrict contributor-level access to trusted users only, minimizing the risk of malicious shortcode injection. 3. Implement Web Application Firewall (WAF) rules to detect and block suspicious shortcode attribute patterns or script tags in user inputs. 4. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on the website. 5. Conduct regular security audits and scanning for XSS vulnerabilities and suspicious shortcode usage in WordPress content. 6. Educate content contributors about safe input practices and the risks of injecting untrusted code. 7. Monitor logs for unusual activity related to shortcode usage or user behavior indicative of exploitation attempts. 8. Consider using security plugins that provide enhanced input sanitization and output escaping for shortcodes and user-generated content.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-25T23:26:23.223Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6960c9cbecefc3cd7c16abb3

Added to database: 1/9/2026, 9:26:35 AM

Last enriched: 2/27/2026, 10:14:39 AM

Last updated: 3/25/2026, 10:38:11 AM

Views: 99

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses