Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
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-10168: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in mucasoft Any News Ticker

0
Medium
VulnerabilityCVE-2025-10168cvecve-2025-10168cwe-79
Published: Tue Sep 30 2025 (09/30/2025, 03:35:31 UTC)
Source: CVE Database V5
Vendor/Project: mucasoft
Product: Any News Ticker

Description

The Any News Ticker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'any-ticker' shortcode in all versions up to, and including, 3.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: 09/30/2025, 04:05:23 UTC

Technical Analysis

CVE-2025-10168 is a stored Cross-Site Scripting (XSS) vulnerability affecting the Any News Ticker WordPress plugin developed by mucasoft. This vulnerability exists in all versions up to and including 3.1.1 due to improper neutralization of input during web page generation, specifically within the 'any-ticker' shortcode. Authenticated users with contributor-level permissions or higher can exploit this flaw by injecting malicious scripts into the shortcode attributes. Because the plugin fails to adequately sanitize and escape user-supplied input, these scripts are stored and later executed in the context of any user who views the affected page. The vulnerability has a CVSS 3.1 base score of 6.4, indicating a medium severity level. The attack vector is network-based with low attack complexity, requiring privileges equivalent to contributor access but no user interaction for exploitation. The scope is changed, meaning the vulnerability can affect resources beyond the initially compromised component. The impact includes limited confidentiality and integrity loss but no availability impact. Stored XSS can lead to session hijacking, defacement, or redirection to malicious sites, potentially compromising user accounts and site integrity. No known exploits are currently reported in the wild, and no patches have been linked yet. This vulnerability is particularly concerning for WordPress sites that use the Any News Ticker plugin and allow contributor-level users to add or edit content, as it can be leveraged to escalate attacks against site administrators or visitors.

Potential Impact

For European organizations, this vulnerability poses a moderate risk, especially for those relying on WordPress sites with the Any News Ticker plugin installed. Exploitation could lead to unauthorized script execution in the browsers of site administrators or visitors, potentially resulting in credential theft, session hijacking, or unauthorized actions performed on behalf of legitimate users. This could compromise sensitive organizational data, damage reputation, and violate data protection regulations such as GDPR if personal data is exposed or manipulated. The risk is heightened in sectors with high web presence like media, e-commerce, and public institutions. Since contributor-level access is required, insider threats or compromised contributor accounts could facilitate exploitation. The stored nature of the XSS means the malicious payload persists, increasing the window of exposure. However, the absence of known active exploits and the medium severity score suggest the threat is manageable with timely mitigation.

Mitigation Recommendations

European organizations should immediately audit their WordPress installations to identify the presence of the Any News Ticker plugin and verify the version in use. Until an official patch is released, organizations should restrict contributor-level permissions to trusted users only and consider temporarily disabling or removing the plugin to eliminate the attack surface. Implementing a Web Application Firewall (WAF) with rules to detect and block malicious script injections targeting the 'any-ticker' shortcode can provide interim protection. Additionally, applying strict Content Security Policy (CSP) headers can limit the impact of injected scripts by restricting script execution sources. Regularly monitoring logs for unusual shortcode usage or unexpected content changes can help detect attempts to exploit this vulnerability. Once a patch is available, prompt application is critical. Educating content contributors about safe input practices and the risks of XSS can further reduce exploitation likelihood.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-09-09T13:34:56.283Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68db52aea473ffe031e44794

Added to database: 9/30/2025, 3:46:54 AM

Last enriched: 9/30/2025, 4:05:23 AM

Last updated: 10/7/2025, 4:22:37 AM

Views: 32

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 are available only with a Pro account. Contact root@offseq.com for access.

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