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-11502: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in magazine3 Schema & Structured Data for WP & AMP

0
Medium
VulnerabilityCVE-2025-11502cvecve-2025-11502cwe-79
Published: Sat Nov 01 2025 (11/01/2025, 05:40:24 UTC)
Source: CVE Database V5
Vendor/Project: magazine3
Product: Schema & Structured Data for WP & AMP

Description

The Schema & Structured Data for WP & AMP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'saswp_tiny_multiple_faq' shortcode in all versions up to, and including, 1.51 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: 11/10/2025, 02:32:46 UTC

Technical Analysis

CVE-2025-11502 is a stored cross-site scripting vulnerability identified in the Schema & Structured Data for WP & AMP plugin for WordPress, specifically in the 'saswp_tiny_multiple_faq' shortcode. This vulnerability arises from improper neutralization of input (CWE-79), where user-supplied attributes are not sufficiently sanitized or escaped before being rendered in web pages. Authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript code into pages generated by the plugin. Because the malicious script is stored persistently, it executes whenever any user accesses the infected page, potentially compromising user sessions, stealing cookies, or performing unauthorized actions on behalf of users. The vulnerability affects all versions up to and including 1.51 of the plugin. The CVSS 3.1 base score is 6.4, reflecting network attack vector, low attack complexity, requiring privileges (contributor or above), no user interaction, and partial impact on confidentiality and integrity but no impact on availability. No patches or exploit code are currently publicly available, but the vulnerability is published and should be addressed promptly. The plugin is widely used in WordPress sites to enhance SEO and structured data presentation, making this vulnerability relevant for many websites relying on this plugin for FAQ schema markup and AMP compatibility.

Potential Impact

For European organizations, this vulnerability poses a significant risk to websites using the affected plugin, especially those that allow contributor-level users to publish or edit content. Exploitation could lead to session hijacking, unauthorized actions, defacement, or distribution of malware via injected scripts. This can damage brand reputation, lead to data breaches involving user credentials or personal data, and potentially violate GDPR requirements regarding data protection and breach notification. E-commerce, media, and public sector websites are particularly vulnerable due to their reliance on WordPress and structured data for SEO and accessibility. The persistent nature of stored XSS means that once exploited, the malicious code can affect all visitors, amplifying the impact. Although no known exploits are currently reported, the medium severity score and ease of exploitation by authenticated users necessitate proactive mitigation to avoid potential attacks.

Mitigation Recommendations

1. Immediately update the Schema & Structured Data for WP & AMP plugin to a version that addresses this vulnerability once available. 2. Until a patch is released, restrict contributor-level and higher privileges to trusted users only, minimizing the risk of malicious content injection. 3. Implement a Web Application Firewall (WAF) with rules to detect and block suspicious script injections in shortcode attributes. 4. Conduct regular security audits and content reviews to detect and remove any injected malicious scripts. 5. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on affected websites. 6. Educate content contributors about safe content practices and the risks of injecting untrusted code. 7. Monitor logs and user activity for unusual behavior indicative of exploitation attempts. 8. Consider disabling or replacing the plugin if immediate patching is not feasible, especially for high-risk sites.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-08T14:28:01.206Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69059f2e1e4a8d05dce595c4

Added to database: 11/1/2025, 5:48:30 AM

Last enriched: 11/10/2025, 2:32:46 AM

Last updated: 12/13/2025, 5:49:14 PM

Views: 87

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats