CVE-2025-13608
Stored XSS in CC Child Pages WordPress Plugin Allows Script Injection
Publication date: 2025-12-15
Last updated on: 2025-12-15
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | cc_child_pages | 2.0.1 |
| wordpress | cc_child_pages | 2.0.0 |
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
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the CC Child Pages WordPress plugin (up to version 2.0.0). It occurs because the plugin does not properly sanitize and escape user-supplied input in certain shortcode attributes (use_custom_link, use_custom_link_target, use_custom_thumbs, and use_custom_excerpt). Authenticated users with contributor-level access or higher can inject malicious scripts into pages, which then execute whenever any user views those pages. [2]
How can this vulnerability impact me? :
This vulnerability can allow attackers with contributor-level access to inject malicious scripts into pages on a WordPress site using the CC Child Pages plugin. These scripts can execute in the browsers of users who visit the infected pages, potentially leading to theft of user credentials, session hijacking, defacement, or other malicious actions. It compromises the integrity and security of the website and its users. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying if the WordPress site is running the cc-child-pages plugin version 2.0.0 or earlier, as these versions are vulnerable. You can check the plugin version via WordPress admin dashboard or by inspecting the plugin files. Additionally, scanning for stored XSS payloads in pages using the 'child_pages' shortcode with attributes like use_custom_link, use_custom_link_target, use_custom_thumbs, or use_custom_excerpt may help detect exploitation. There are no specific commands provided in the resources for detection. [2]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the cc-child-pages plugin to version 2.0.1 or later, which includes security fixes that properly sanitize and escape user-supplied input to prevent stored cross-site scripting. Additionally, ensure that only trusted users have contributor or higher access, and consider reviewing and cleaning any pages that may have been injected with malicious scripts. [2]