CVE-2025-13705
Stored XSS in WordPress Custom Frames Plugin Allows Script Injection
Publication date: 2025-12-13
Last updated on: 2025-12-13
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | custom_frames | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for instances where the 'customframe' shortcode is used with a 'class' parameter containing suspicious or malicious script code in WordPress posts or pages. Additionally, monitoring HTTP requests and responses for injected scripts in pages using the Custom Frames plugin may help detect exploitation. Specific commands could include using WP-CLI to search posts for the shortcode with suspicious attributes, e.g., `wp post list --post_type=page,post --field=ID | xargs -I % wp post get % --field=post_content | grep '\[customframe.*class=.*<script>'` to find potential injected scripts. Network monitoring tools can also be used to detect unexpected JavaScript payloads in responses from the affected site. [1, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows authenticated attackers with Contributor-level access to inject arbitrary scripts via stored Cross-Site Scripting (XSS). This can lead to unauthorized access to user data or session hijacking, which may result in violations of data protection regulations such as GDPR or HIPAA that require safeguarding personal and sensitive information. Therefore, the presence of this vulnerability could negatively impact compliance with these standards by exposing protected data to attackers. [3]
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the Custom Frames plugin for WordPress. It occurs via the 'class' parameter of the 'customframe' shortcode in versions up to 1.0.1. Because of insufficient input sanitization and output escaping, authenticated users with Contributor-level access or higher can inject malicious scripts into pages. These scripts execute whenever any user accesses the affected page.
How can this vulnerability impact me? :
The vulnerability allows attackers with Contributor-level access or above to inject arbitrary web scripts into pages. This can lead to unauthorized actions such as stealing user credentials, session hijacking, defacement, or spreading malware to users who visit the infected pages.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Custom Frames plugin to a version later than 1.0.1 where the vulnerability is fixed. If an update is not available, restrict Contributor-level and above users from adding or editing content with the 'customframe' shortcode, or disable the plugin temporarily. Additionally, sanitize and validate all inputs related to the 'class' parameter in the shortcode and ensure output escaping is properly implemented to prevent script injection. Monitoring and cleaning any existing injected scripts in the site content is also recommended. [1, 3]