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-10130: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in stripeswp Layers

0
Medium
VulnerabilityCVE-2025-10130cvecve-2025-10130cwe-79
Published: Tue Sep 30 2025 (09/30/2025, 03:35:25 UTC)
Source: CVE Database V5
Vendor/Project: stripeswp
Product: Layers

Description

CVE-2025-10130 is a stored Cross-Site Scripting (XSS) vulnerability in the Layers WordPress plugin by stripeswp, affecting all versions up to 0. 5. It arises from improper input sanitization and output escaping on the 'webcam' shortcode attributes, allowing authenticated users with contributor-level access or higher to inject malicious scripts. These scripts execute whenever any user views the compromised page, potentially leading to session hijacking, defacement, or further attacks. The vulnerability has a CVSS score of 6. 4 (medium severity) and does not require user interaction but does require authenticated access. No known exploits are currently reported in the wild. European organizations using this plugin on WordPress sites are at risk, especially those with contributor-level user roles enabled. Mitigation involves promptly updating or patching the plugin once available, restricting contributor permissions, and implementing web application firewalls with XSS detection capabilities.

AI-Powered Analysis

AILast updated: 10/07/2025, 11:39:11 UTC

Technical Analysis

CVE-2025-10130 is a stored Cross-Site Scripting vulnerability identified in the Layers plugin for WordPress, developed by stripeswp. The vulnerability exists in all versions up to and including 0.5, specifically in the handling of the 'webcam' shortcode. The root cause is insufficient sanitization and output escaping of user-supplied attributes within this shortcode, which allows an authenticated attacker with contributor-level or higher privileges to inject arbitrary JavaScript code into pages. When any user accesses a page containing the injected script, the malicious code executes in their browser context. This can lead to a range of attacks including session hijacking, privilege escalation, defacement, or distribution of malware. The vulnerability requires authentication but no user interaction beyond viewing the affected page. The CVSS 3.1 base score is 6.4, reflecting medium severity with network attack vector, low attack complexity, and partial impact on confidentiality and integrity but no impact on availability. No patches or known exploits are currently available, but the vulnerability is publicly disclosed and assigned by Wordfence. The scope is limited to WordPress sites using the Layers plugin with the vulnerable shortcode enabled and contributor-level users able to add or modify content. This vulnerability highlights the importance of proper input validation and output encoding in web applications, especially in CMS plugins that accept user-generated content.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to websites running WordPress with the Layers plugin installed. The ability for contributors to inject persistent malicious scripts can lead to unauthorized access to user sessions, theft of sensitive data, or defacement of public-facing websites. This can damage organizational reputation, lead to data breaches, and potentially facilitate further attacks within the network. Sectors with high reliance on WordPress for public communication, such as media, education, and small to medium enterprises, are particularly vulnerable. The requirement for contributor-level access limits the risk to organizations with lax user permission controls or those that allow external contributors. However, given the widespread use of WordPress across Europe and the popularity of plugins, the attack surface is significant. The vulnerability does not impact availability but can compromise confidentiality and integrity of web content and user data. Regulatory implications under GDPR may arise if personal data is compromised through this vector.

Mitigation Recommendations

1. Immediately audit WordPress installations to identify the presence of the Layers plugin and determine the version in use. 2. Restrict contributor-level permissions to trusted users only and review user roles to minimize unnecessary privileges. 3. Until an official patch is released, disable or remove the 'webcam' shortcode functionality if possible to prevent exploitation. 4. Employ Web Application Firewalls (WAFs) with rules to detect and block common XSS payloads, especially targeting the plugin's shortcode parameters. 5. Implement Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on affected sites. 6. Monitor logs and user activity for suspicious content creation or modification indicative of exploitation attempts. 7. Once a patch or update is available from stripeswp, apply it promptly and verify the fix. 8. Educate content contributors about the risks of injecting untrusted content and enforce secure content creation policies. 9. Conduct regular vulnerability scanning and penetration testing focused on CMS plugins and user input handling. 10. Backup website data regularly to enable quick restoration in case of compromise.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-09-08T19:25:42.244Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68db52aea473ffe031e4478b

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

Last enriched: 10/7/2025, 11:39:11 AM

Last updated: 11/22/2025, 3:19:59 PM

Views: 23

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