CVE-2025-7694: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in WofficeIO Woffice Core
The Woffice Core plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the woffice_file_manager_delete() function in all versions up to, and including, 5.4.26. This makes it possible for authenticated attackers, with Contributor-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).
AI Analysis
Technical Summary
CVE-2025-7694 is a path traversal vulnerability classified under CWE-22 affecting the Woffice Core plugin for WordPress. This vulnerability arises from insufficient validation of file paths in the woffice_file_manager_delete() function, present in all versions up to and including 5.4.26. Authenticated attackers with Contributor-level access or higher can exploit this flaw to delete arbitrary files on the server. The lack of proper pathname restrictions allows attackers to traverse directories and specify files outside the intended directory scope. By deleting critical files such as wp-config.php, attackers can disrupt the WordPress installation, potentially leading to remote code execution or complete site compromise. The vulnerability has a CVSS 3.1 base score of 6.8, indicating a medium severity level. The attack vector is network-based, requiring low privileges (Contributor role), no user interaction, and has a high impact on integrity and availability but no direct confidentiality impact. No known exploits are currently reported in the wild, and no patches have been released at the time of this report. The vulnerability is significant because WordPress is widely used, and Woffice Core is a popular plugin for intranet and extranet sites, making affected installations attractive targets for attackers aiming to disrupt business operations or gain further access.
Potential Impact
For European organizations, this vulnerability poses a considerable risk, especially for those relying on WordPress with the Woffice Core plugin for internal collaboration or client-facing portals. Successful exploitation can lead to deletion of critical files, causing service outages, data loss, and potential escalation to remote code execution, which can compromise entire web servers. This can disrupt business continuity, damage reputation, and lead to regulatory non-compliance under GDPR if personal data is affected or availability is impacted. Organizations in sectors such as finance, healthcare, education, and government, which often use WordPress-based intranet solutions, may face heightened risks. The requirement for only Contributor-level access lowers the barrier for insider threats or compromised accounts to exploit this vulnerability, increasing the attack surface. Additionally, the lack of patches means organizations must rely on mitigation until an official fix is available.
Mitigation Recommendations
European organizations should immediately audit their WordPress installations to identify the presence of the Woffice Core plugin and verify the version in use. Until a patch is released, the following specific mitigations are recommended: 1) Restrict Contributor-level access strictly to trusted users and review user permissions to minimize the number of users with such privileges. 2) Implement Web Application Firewall (WAF) rules to detect and block suspicious file deletion requests or path traversal patterns targeting the woffice_file_manager_delete() endpoint. 3) Employ file integrity monitoring to detect unauthorized deletions or modifications of critical files such as wp-config.php. 4) Regularly back up WordPress files and databases to enable rapid restoration in case of file deletion. 5) Consider temporarily disabling or removing the Woffice Core plugin if it is not essential. 6) Monitor logs for unusual activity related to file deletions or Contributor account actions. 7) Prepare to apply patches promptly once released by the vendor. These targeted steps go beyond generic advice by focusing on access control, detection, and recovery specific to this vulnerability's exploitation vector.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Belgium, Sweden, Austria
CVE-2025-7694: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in WofficeIO Woffice Core
Description
The Woffice Core plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the woffice_file_manager_delete() function in all versions up to, and including, 5.4.26. This makes it possible for authenticated attackers, with Contributor-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).
AI-Powered Analysis
Technical Analysis
CVE-2025-7694 is a path traversal vulnerability classified under CWE-22 affecting the Woffice Core plugin for WordPress. This vulnerability arises from insufficient validation of file paths in the woffice_file_manager_delete() function, present in all versions up to and including 5.4.26. Authenticated attackers with Contributor-level access or higher can exploit this flaw to delete arbitrary files on the server. The lack of proper pathname restrictions allows attackers to traverse directories and specify files outside the intended directory scope. By deleting critical files such as wp-config.php, attackers can disrupt the WordPress installation, potentially leading to remote code execution or complete site compromise. The vulnerability has a CVSS 3.1 base score of 6.8, indicating a medium severity level. The attack vector is network-based, requiring low privileges (Contributor role), no user interaction, and has a high impact on integrity and availability but no direct confidentiality impact. No known exploits are currently reported in the wild, and no patches have been released at the time of this report. The vulnerability is significant because WordPress is widely used, and Woffice Core is a popular plugin for intranet and extranet sites, making affected installations attractive targets for attackers aiming to disrupt business operations or gain further access.
Potential Impact
For European organizations, this vulnerability poses a considerable risk, especially for those relying on WordPress with the Woffice Core plugin for internal collaboration or client-facing portals. Successful exploitation can lead to deletion of critical files, causing service outages, data loss, and potential escalation to remote code execution, which can compromise entire web servers. This can disrupt business continuity, damage reputation, and lead to regulatory non-compliance under GDPR if personal data is affected or availability is impacted. Organizations in sectors such as finance, healthcare, education, and government, which often use WordPress-based intranet solutions, may face heightened risks. The requirement for only Contributor-level access lowers the barrier for insider threats or compromised accounts to exploit this vulnerability, increasing the attack surface. Additionally, the lack of patches means organizations must rely on mitigation until an official fix is available.
Mitigation Recommendations
European organizations should immediately audit their WordPress installations to identify the presence of the Woffice Core plugin and verify the version in use. Until a patch is released, the following specific mitigations are recommended: 1) Restrict Contributor-level access strictly to trusted users and review user permissions to minimize the number of users with such privileges. 2) Implement Web Application Firewall (WAF) rules to detect and block suspicious file deletion requests or path traversal patterns targeting the woffice_file_manager_delete() endpoint. 3) Employ file integrity monitoring to detect unauthorized deletions or modifications of critical files such as wp-config.php. 4) Regularly back up WordPress files and databases to enable rapid restoration in case of file deletion. 5) Consider temporarily disabling or removing the Woffice Core plugin if it is not essential. 6) Monitor logs for unusual activity related to file deletions or Contributor account actions. 7) Prepare to apply patches promptly once released by the vendor. These targeted steps go beyond generic advice by focusing on access control, detection, and recovery specific to this vulnerability's exploitation vector.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-07-15T20:01:09.691Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 688d8a60ad5a09ad00d0f58e
Added to database: 8/2/2025, 3:47:44 AM
Last enriched: 8/2/2025, 4:02:44 AM
Last updated: 8/2/2025, 12:03:44 PM
Views: 8
Related Threats
CVE-2025-7710: CWE-288 Authentication Bypass Using an Alternate Path or Channel in Brave Brave Conversion Engine (PRO)
CriticalCVE-2025-7500: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in oceanwp Ocean Social Sharing
MediumCVE-2025-8467: SQL Injection in code-projects Wazifa System
MediumCVE-2025-8488: CWE-862 Missing Authorization in brainstormforce Ultimate Addons for Elementor (Formerly Elementor Header & Footer Builder)
MediumCVE-2025-6722: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in bitslip6 BitFire Security – Firewall, WAF, Bot/Spam Blocker, Login Security
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.