CVE-2025-7658
BaseFortify
Publication date: 2025-07-19
Last updated on: 2025-07-22
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | temporarily_hidden_content | * |
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 exists in the Temporarily Hidden Content WordPress plugin (up to version 1.0.6) and is a Stored Cross-Site Scripting (XSS) issue. It occurs because the plugin does not properly sanitize or escape user-supplied attributes in its 'temphc-start' shortcode. As a result, authenticated users with contributor-level access or higher can inject malicious scripts into pages. These scripts will execute whenever any user accesses the infected page, potentially compromising user data or site integrity.
How can this vulnerability impact me? :
The vulnerability allows attackers with contributor-level access or above to inject arbitrary web scripts into pages via the plugin's shortcode. This can lead to malicious scripts executing in the browsers of users who visit those pages. Potential impacts include theft of user credentials, session hijacking, defacement, or other malicious activities that compromise the security and integrity of the website and its users.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by scanning WordPress installations for the presence of the Temporarily Hidden Content plugin version 1.0.6 or earlier. Additionally, inspecting pages or posts for the use of the 'temphc-start' shortcode with suspicious or unexpected attributes may indicate exploitation attempts. Since the vulnerability involves stored cross-site scripting via shortcode attributes, monitoring HTTP requests and responses for injected scripts in pages containing this shortcode can help detect exploitation. Specific commands are not provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Temporarily Hidden Content plugin to a version later than 1.0.6 where the vulnerability is fixed. If an update is not available, restrict contributor-level and higher users from adding or editing content with the 'temphc-start' shortcode to prevent injection of malicious scripts. Additionally, implement web application firewall (WAF) rules to detect and block cross-site scripting payloads related to this plugin's shortcode attributes. [1]