CVE-2025-13725
BaseFortify
Publication date: 2026-01-17
Last updated on: 2026-01-17
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| thimpress | thim-blocks | to 1.0.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized disclosure of sensitive server files, including configuration files like wp-config.php, which may contain database credentials and other critical information. This can compromise the security of the WordPress site and potentially lead to further attacks or data breaches.
Can you explain this vulnerability to me?
This vulnerability exists in the Gutenberg Thim Blocks – Page Builder plugin for WordPress, versions up to and including 1.0.1. It allows authenticated users with Contributor-level access or higher to read arbitrary files on the server. This is possible due to insufficient path validation in the server-side rendering of the 'thim-blocks/icon' block, specifically via the 'iconSVG' parameter. Attackers can exploit this to access sensitive files such as wp-config.php.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can negatively impact compliance with standards such as GDPR and HIPAA because unauthorized access to sensitive files may lead to exposure of personal or protected data. Such data breaches can result in violations of data protection regulations, leading to legal and financial consequences.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the Gutenberg Thim Blocks plugin to version 1.0.2 or later, as this is the next released version after 1.0.1. Although the changeset for version 1.0.2 does not explicitly describe security fixes for CVE-2025-13725, updating to the latest version is recommended to ensure any potential fixes or improvements are applied. [1]