CVE-2025-5541
BaseFortify
Publication date: 2025-06-06
Last updated on: 2025-06-06
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
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?
The vulnerability in the Runners Log WordPress plugin is a Stored Cross-Site Scripting (XSS) issue that occurs via the 'runnerslog' shortcode. It affects all versions up to and including 3.9.2. The problem arises because the plugin does not properly sanitize or escape user-supplied attributes in the shortcode. This allows authenticated users with contributor-level access or higher to inject malicious scripts into pages. These scripts then execute whenever any user views the infected page.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with contributor-level access or above to inject arbitrary JavaScript code into pages on a WordPress site using the Runners Log plugin. When other users visit these pages, the malicious scripts execute in their browsers, potentially leading to session hijacking, defacement, unauthorized actions on behalf of users, or theft of sensitive information. Since the attack requires authenticated access, it can be used to escalate the impact within the site.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying if the Runners Log WordPress plugin is installed and its version is 3.9.2 or earlier. Since the vulnerability involves stored Cross-Site Scripting via the 'runnerslog' shortcode, detection can include searching for the presence of this shortcode in WordPress posts or pages. Additionally, monitoring HTTP requests and responses for injected scripts in pages using the 'runnerslog' shortcode can help detect exploitation attempts. Specific commands to detect the plugin version or shortcode usage might include: 1) Using WP-CLI to check plugin version: `wp plugin list --format=json | jq '.[] | select(.name=="runners-log")'` 2) Searching the WordPress database for usage of the shortcode: `wp db query "SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%[runnerslog%'"` 3) Using network monitoring tools (e.g., tcpdump, Wireshark) to inspect HTTP traffic for suspicious script injections. However, no explicit detection commands are provided in the resources.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Runners Log plugin to a version later than 3.9.2 where the vulnerability is fixed. If an update is not immediately available, restrict contributor-level and higher user permissions to trusted users only, as the vulnerability requires authenticated users with contributor-level access or above to exploit. Additionally, consider disabling or removing the 'runnerslog' shortcode usage in posts/pages until a patch is applied. Implementing Web Application Firewall (WAF) rules to block malicious script injections targeting the shortcode may also help mitigate exploitation.