Skip to main content

CVE-2025-7957: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in surror ShortcodeHub – MultiPurpose Shortcode Builder

Medium
VulnerabilityCVE-2025-7957cvecve-2025-7957cwe-79
Published: Sat Aug 23 2025 (08/23/2025, 04:25:49 UTC)
Source: CVE Database V5
Vendor/Project: surror
Product: ShortcodeHub – MultiPurpose Shortcode Builder

Description

The ShortcodeHub plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘author_link_target’ parameter in all versions up to, and including, 1.7.1 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: 08/23/2025, 04:48:33 UTC

Technical Analysis

CVE-2025-7957 is a stored Cross-Site Scripting (XSS) vulnerability affecting the ShortcodeHub – MultiPurpose Shortcode Builder plugin for WordPress, developed by surror. This vulnerability exists in all versions up to and including 1.7.1 due to improper neutralization of input during web page generation, specifically involving the 'author_link_target' parameter. The root cause is insufficient input sanitization and output escaping, allowing an authenticated user with Contributor-level access or higher to inject arbitrary malicious scripts into pages. These scripts are stored persistently and executed whenever any user accesses the compromised page, potentially leading to session hijacking, privilege escalation, or redirection to malicious sites. The vulnerability has a CVSS v3.1 base score of 6.4, indicating a medium severity level. The attack vector is network-based (remote), requires low attack complexity, and privileges at the Contributor level, but no user interaction is needed for exploitation. The scope is changed, meaning the vulnerability can affect resources beyond the initially vulnerable component. While no known exploits are currently reported in the wild, the vulnerability poses a significant risk due to the widespread use of WordPress and the plugin's functionality. The absence of patches at the time of publication increases the urgency for mitigation. Stored XSS vulnerabilities are particularly dangerous as they can affect multiple users and lead to persistent compromise of website integrity and user trust.

Potential Impact

For European organizations, this vulnerability can lead to unauthorized script execution on their WordPress-powered websites, potentially compromising user data confidentiality and integrity. Attackers could steal session cookies, impersonate users, or perform unauthorized actions within the site context. This is especially critical for organizations handling sensitive customer information, e-commerce platforms, and public-facing portals. The persistent nature of stored XSS means that multiple users, including administrators, could be affected, amplifying the risk. Additionally, exploitation could damage the organization's reputation, lead to regulatory non-compliance (e.g., GDPR violations if personal data is exposed), and cause operational disruptions. Given the medium severity and the requirement for authenticated access, insider threats or compromised contributor accounts could be leveraged to exploit this vulnerability. The lack of user interaction needed for exploitation increases the risk of automated or stealthy attacks. Overall, the vulnerability could facilitate further attacks such as phishing, malware distribution, or privilege escalation within the affected websites.

Mitigation Recommendations

European organizations using the ShortcodeHub plugin should immediately audit their WordPress installations to identify affected versions (up to 1.7.1). Since no official patches are currently available, organizations should consider the following specific mitigations: 1) Restrict Contributor-level access strictly to trusted users and review existing user roles and permissions to minimize the attack surface. 2) Implement Web Application Firewall (WAF) rules to detect and block suspicious input patterns targeting the 'author_link_target' parameter. 3) Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts. 4) Regularly monitor website content for unauthorized script injections and unusual behavior. 5) Consider temporarily disabling or replacing the ShortcodeHub plugin with alternative solutions until a patch is released. 6) Educate content contributors about secure input practices and the risks of injecting untrusted content. 7) Keep WordPress core and all plugins updated to the latest versions to reduce exposure to known vulnerabilities. 8) Prepare an incident response plan to quickly address any detected exploitation attempts.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-07-21T13:20:20.335Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68a9446fad5a09ad00269547

Added to database: 8/23/2025, 4:32:47 AM

Last enriched: 8/23/2025, 4:48:33 AM

Last updated: 8/23/2025, 7:29:57 AM

Views: 5

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