CVE-2025-13725: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in thimpress Thim Blocks
The Gutenberg Thim Blocks – Page Builder, Gutenberg Blocks for the Block Editor plugin for WordPress is vulnerable to arbitrary file reads in all versions up to, and including, 1.0.1. This is due to insufficient path validation in the server-side rendering of the thim-blocks/icon block. This makes it possible for authenticated attackers, with Contributor-level access and above, to read the contents of arbitrary files on the server via the 'iconSVG' parameter, which can contain sensitive information such as wp-config.php.
AI Analysis
Technical Summary
CVE-2025-13725 is a path traversal vulnerability (CWE-22) found in the Thim Blocks – Page Builder plugin for WordPress, specifically in the server-side rendering logic of the thim-blocks/icon block. The vulnerability arises due to insufficient validation of the 'iconSVG' parameter, which is used to specify SVG icons. Authenticated attackers with Contributor-level privileges or higher can manipulate this parameter to traverse directories and read arbitrary files on the server filesystem. This can lead to exposure of sensitive files such as wp-config.php, which contains database credentials and other critical configuration details. The vulnerability affects all versions up to and including 1.0.1 of the plugin. Exploitation does not require user interaction beyond authentication, and the attack vector is network-based with low attack complexity. The CVSS v3.1 score is 6.5, reflecting a medium severity with high confidentiality impact but no impact on integrity or availability. No patches or fixes are currently linked, and no known exploits have been reported in the wild as of the publication date. The vulnerability was reserved in late 2025 and published in early 2026. The plugin is used in WordPress environments, which are widely deployed globally, increasing the potential attack surface.
Potential Impact
The primary impact of this vulnerability is unauthorized disclosure of sensitive server files, including configuration files like wp-config.php that contain database credentials and other secrets. This can lead to further compromise of the WordPress site and underlying infrastructure if attackers leverage the leaked information. Organizations running WordPress sites with the vulnerable Thim Blocks plugin are at risk of data leakage, which can result in loss of confidentiality, reputational damage, and potential compliance violations. Since the vulnerability requires only Contributor-level authentication, it lowers the barrier for exploitation compared to vulnerabilities requiring higher privileges. Although the vulnerability does not directly affect integrity or availability, the information disclosure can be a stepping stone for privilege escalation, lateral movement, or other attacks. The lack of known exploits in the wild suggests limited active exploitation currently, but the widespread use of WordPress and this plugin means the risk remains significant.
Mitigation Recommendations
Organizations should immediately verify if they use the Thim Blocks plugin version 1.0.1 or earlier and plan to update to a patched version once available. In the absence of an official patch, administrators should consider temporarily disabling the plugin or restricting Contributor-level user permissions to trusted users only. Implementing web application firewall (WAF) rules to detect and block path traversal patterns in requests targeting the 'iconSVG' parameter can provide interim protection. Monitoring logs for suspicious access patterns or attempts to read sensitive files is also recommended. Additionally, hardening the server by restricting file permissions to limit access to sensitive files like wp-config.php can reduce the impact of exploitation. Regularly auditing user roles and minimizing the number of users with Contributor or higher privileges will reduce the attack surface. Finally, organizations should stay alert for updates from the vendor and apply patches promptly once released.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, India, Brazil, Japan, Netherlands
CVE-2025-13725: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in thimpress Thim Blocks
Description
The Gutenberg Thim Blocks – Page Builder, Gutenberg Blocks for the Block Editor plugin for WordPress is vulnerable to arbitrary file reads in all versions up to, and including, 1.0.1. This is due to insufficient path validation in the server-side rendering of the thim-blocks/icon block. This makes it possible for authenticated attackers, with Contributor-level access and above, to read the contents of arbitrary files on the server via the 'iconSVG' parameter, which can contain sensitive information such as wp-config.php.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-13725 is a path traversal vulnerability (CWE-22) found in the Thim Blocks – Page Builder plugin for WordPress, specifically in the server-side rendering logic of the thim-blocks/icon block. The vulnerability arises due to insufficient validation of the 'iconSVG' parameter, which is used to specify SVG icons. Authenticated attackers with Contributor-level privileges or higher can manipulate this parameter to traverse directories and read arbitrary files on the server filesystem. This can lead to exposure of sensitive files such as wp-config.php, which contains database credentials and other critical configuration details. The vulnerability affects all versions up to and including 1.0.1 of the plugin. Exploitation does not require user interaction beyond authentication, and the attack vector is network-based with low attack complexity. The CVSS v3.1 score is 6.5, reflecting a medium severity with high confidentiality impact but no impact on integrity or availability. No patches or fixes are currently linked, and no known exploits have been reported in the wild as of the publication date. The vulnerability was reserved in late 2025 and published in early 2026. The plugin is used in WordPress environments, which are widely deployed globally, increasing the potential attack surface.
Potential Impact
The primary impact of this vulnerability is unauthorized disclosure of sensitive server files, including configuration files like wp-config.php that contain database credentials and other secrets. This can lead to further compromise of the WordPress site and underlying infrastructure if attackers leverage the leaked information. Organizations running WordPress sites with the vulnerable Thim Blocks plugin are at risk of data leakage, which can result in loss of confidentiality, reputational damage, and potential compliance violations. Since the vulnerability requires only Contributor-level authentication, it lowers the barrier for exploitation compared to vulnerabilities requiring higher privileges. Although the vulnerability does not directly affect integrity or availability, the information disclosure can be a stepping stone for privilege escalation, lateral movement, or other attacks. The lack of known exploits in the wild suggests limited active exploitation currently, but the widespread use of WordPress and this plugin means the risk remains significant.
Mitigation Recommendations
Organizations should immediately verify if they use the Thim Blocks plugin version 1.0.1 or earlier and plan to update to a patched version once available. In the absence of an official patch, administrators should consider temporarily disabling the plugin or restricting Contributor-level user permissions to trusted users only. Implementing web application firewall (WAF) rules to detect and block path traversal patterns in requests targeting the 'iconSVG' parameter can provide interim protection. Monitoring logs for suspicious access patterns or attempts to read sensitive files is also recommended. Additionally, hardening the server by restricting file permissions to limit access to sensitive files like wp-config.php can reduce the impact of exploitation. Regularly auditing user roles and minimizing the number of users with Contributor or higher privileges will reduce the attack surface. Finally, organizations should stay alert for updates from the vendor and apply patches promptly once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-11-25T22:29:33.290Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 696b0749b22c7ad868788fc2
Added to database: 1/17/2026, 3:51:37 AM
Last enriched: 2/27/2026, 10:14:00 AM
Last updated: 3/26/2026, 4:53:23 AM
Views: 77
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.