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-13899: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in pntrinh TR Timthumb

0
Medium
VulnerabilityCVE-2025-13899cvecve-2025-13899cwe-79
Published: Sat Dec 06 2025 (12/06/2025, 05:49:28 UTC)
Source: CVE Database V5
Vendor/Project: pntrinh
Product: TR Timthumb

Description

The TR Timthumb plugin for WordPress is vulnerable to Stored Cross-Site Scripting via shortcode attributes in all versions up to, and including, 1.0.4 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:10:08 UTC

Technical Analysis

CVE-2025-13899 identifies a stored Cross-Site Scripting (XSS) vulnerability in the TR Timthumb plugin for WordPress, maintained by pntrinh. This vulnerability affects all versions up to and including 1.0.4. The root cause is improper neutralization of input during web page generation, specifically insufficient sanitization and escaping of shortcode attributes. Authenticated users with Contributor-level access or higher can exploit this flaw by injecting arbitrary JavaScript code into shortcode attributes embedded in WordPress pages. When any user subsequently accesses these pages, the malicious scripts execute in their browsers, potentially compromising session tokens, redirecting users, or performing unauthorized actions within the context of the victim’s session. The vulnerability does not require user interaction beyond page access, and the attack scope is limited to sites using the vulnerable plugin. The CVSS 3.1 base score of 6.4 reflects a medium severity, with network attack vector, low attack complexity, requiring privileges but no user interaction, and partial impact on confidentiality and integrity. No patches or official fixes are currently linked, and no known exploits have been reported in the wild. The vulnerability is classified under CWE-79, a common web application security weakness related to Cross-Site Scripting. The plugin’s widespread use in WordPress sites makes this a relevant threat for web administrators and security teams.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of web applications running WordPress with the TR Timthumb plugin. Exploitation can lead to session hijacking, unauthorized actions performed on behalf of users, defacement, or distribution of malware through compromised pages. Organizations with Contributor-level users who can publish or edit content are particularly vulnerable, as these users can inject malicious scripts. This may result in reputational damage, data breaches involving user credentials or personal data, and potential regulatory non-compliance under GDPR if personal data is compromised. The medium severity indicates that while the vulnerability is exploitable remotely, it requires authenticated access, somewhat limiting the attack surface. However, given the popularity of WordPress in Europe and the common use of plugins for site customization, many organizations could be exposed. Attackers targeting media, e-commerce, or governmental websites could leverage this vulnerability for persistent attacks or lateral movement within networks.

Mitigation Recommendations

1. Immediately update the TR Timthumb plugin to a version that addresses this vulnerability once available. If no patch exists, consider disabling or removing the plugin until a fix is released. 2. Restrict Contributor-level and higher privileges to trusted users only, minimizing the risk of malicious script injection. 3. Implement strict input validation and output encoding for all shortcode attributes and user-generated content to prevent script injection. 4. Employ Web Application Firewalls (WAFs) with rules to detect and block XSS payloads targeting shortcode parameters. 5. Conduct regular security audits and code reviews of WordPress plugins and themes to identify similar vulnerabilities. 6. Educate content contributors about safe content practices and the risks of injecting untrusted code. 7. Monitor web server logs and user activity for unusual behavior indicative of exploitation attempts. 8. Use Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts on web pages. These steps collectively reduce the likelihood and impact of exploitation beyond generic patching advice.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-02T16:14:03.217Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6933c72011163305efef427d

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

Last enriched: 12/13/2025, 7:10:08 AM

Last updated: 1/20/2026, 6:26:52 PM

Views: 68

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