CVE-2026-7547: Path Traversal in Woosa Marktplaats WooCommerce Plugin – Admin File Read Risk
The Woosa – Marktplaats for WooCommerce plugin contains a path traversal vulnerability that allows authenticated site administrators to read sensitive files from the server, such as the WordPress configuration file. An attacker with admin credentials can manipulate a file parameter to escape the plugin's intended log directory and access arbitrary files, potentially exposing database credentials and other secrets stored in wp-config.php.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 4.9 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- Weaknesses (CWE)
- CWE-22
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-19 / 2026-06-23
NVD description (verbatim)
The Woosa – Marktplaats for WooCommerce plugin for WordPress is vulnerable to Arbitrary File Read via Path Traversal in versions up to and including 2.0.4. This is due to insufficient path sanitization in the render_logs_ui() function, which accepts a base64-encoded file name from the 'log_file' GET parameter and concatenates it directly with the plugin's log directory path without validating that the resolved path remains within the intended directory. This makes it possible for authenticated attackers, with Administrator-level access, to read the contents of arbitrary files on the server, including wp-config.
8 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-7547 is a Path Traversal vulnerability (CWE-22) in the Woosa – Marktplaats for WooCommerce plugin versions up to 2.0.4. The render_logs_ui() function accepts a base64-encoded file name via the 'log_file' GET parameter and concatenates it directly to the plugin's log directory path without path canonicalization or boundary validation. This allows an authenticated administrator to traverse upward in the directory tree and read arbitrary files. The CVSS 3.1 score of 4.9 (MEDIUM) reflects the requirement for authenticated Administrator-level access, though the impact on confidentiality is high.
Business impact
If an administrator account is compromised or an insider has malicious intent, they can extract the WordPress database credentials, API keys, and other secrets from wp-config.php. This could facilitate further lateral movement, data exfiltration, or credential harvesting. For multi-tenant or managed WordPress hosting environments, this escalates risk significantly. The business impact depends on defense-in-depth controls: if admin access is already granted, the threat surface is narrower, but the confidentiality breach is severe.
Affected systems
WordPress installations running the Woosa – Marktplaats for WooCommerce plugin in any version up to and including 2.0.4. This plugin is designed for integration with Marktplaats, a Dutch online marketplace. The vulnerability requires administrator-level authentication, so only sites with compromised or rogue admin accounts are at immediate risk.
Exploitability
The vulnerability requires Administrator-level access to WordPress, making opportunistic exploitation unlikely for external threat actors. However, the attack is trivial to execute once admin credentials are obtained: base64-encode a traversal path like '../../../../wp-config.php', pass it as the 'log_file' parameter, and retrieve the file contents. No user interaction is required. Insider threats or accounts compromised through phishing, credential stuffing, or weak passwords present the principal risk vector.
Remediation
Update the Woosa – Marktplaats for WooCommerce plugin to a version that implements proper path sanitization and validates that the decoded and resolved file path remains within the intended log directory. Verify the patched version against the vendor's advisory. Additionally, enforce strong password policies for administrator accounts, implement two-factor authentication (2FA), and restrict admin account creation to trusted personnel only.
Patch guidance
Check the Woosa plugin's official update mechanism in the WordPress admin dashboard or the WordPress plugin repository for a patched version addressing CVE-2026-7547. Verify against the vendor's official security advisory to confirm the fix includes canonical path resolution and strict boundary validation. After patching, test that the log file viewer functions normally and that path traversal attempts are blocked.
Detection guidance
Monitor web server and WordPress logs for GET requests to the plugin's render_logs_ui endpoint containing suspicious 'log_file' parameters, particularly those with base64-encoded traversal sequences (e.g., ../ patterns after decoding). Audit recent administrator account logins and privilege escalations. Review file access logs for unexpected reads of wp-config.php or other sensitive files by the web server process. Implement WAF rules to block requests with path traversal indicators in plugin parameters.
Why prioritize this
Although the CVSS score is MEDIUM (4.9), the practical risk is context-dependent. If your WordPress admin accounts are well-protected and monitored, remediation can follow standard patching windows. However, if admin accounts have been reused, shared, or are accessed from untrusted networks, this should be elevated to high priority, as the confidentiality impact is severe and file contents are directly exfiltrable without additional exploitation steps.
Risk score, explained
The CVSS 3.1 score of 4.9 reflects: Network-based attack vector (AV:N), low attack complexity (AC:L), high privilege requirement (PR:H), no user interaction (UI:N), and unchanged scope (S:U). The confidentiality impact is high (C:H), but integrity and availability are not affected (I:N, A:N). The high privilege barrier and absence from the Known Exploited Vulnerabilities (KEV) catalog keep the score in the MEDIUM band, but organizations should not underestimate the risk if admin credentials are at risk.
Frequently asked questions
Why does this require Administrator access if it's a serious vulnerability?
Path traversal vulnerabilities are dangerous regardless of access level, but Administrator privileges narrow the threat model. The concern is credential compromise, insider threats, or security gaps in how admin accounts are managed. If admin access is never exposed, the risk is mitigated; however, in many organizations, multiple people have admin rights, increasing the surface.
How do I check if my site has been exploited?
Review web server access logs for requests containing the 'log_file' GET parameter to the plugin, especially with base64-encoded values. Check for unauthorized reads of wp-config.php or similar files using file integrity monitoring. If your WordPress activity logs record admin logins you don't recognize, immediately investigate credential compromise.
Is there a workaround if I cannot patch immediately?
Restrict plugin functionality or disable the log viewer feature via code until a patch is available. Implement strong access controls: use 2FA for all admin accounts, limit admin IPs via firewall rules, and deactivate unused admin accounts. These mitigations reduce the likelihood that an attacker can exploit this vulnerability.
Does this affect non-administrators using the plugin?
No. The vulnerability specifically requires Administrator-level authentication. Regular users, customers, and non-admin site users cannot exploit this flaw directly.
This analysis is provided for informational purposes by SEC.co. It is not a substitute for your organization's security team assessment or vendor advisories. Always verify patch versions and compatibility against the vendor's official security bulletins before deploying updates. The vulnerability requires Administrator-level access; however, security posture should be evaluated holistically, including the risk of credential compromise. If you have specific concerns about your environment, consult a qualified security professional. Source: NVD (public-domain), retrieved 2026-07-28. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2018-25393MEDIUMNavigate CMS 2.8.5 Path Traversal Vulnerability (CVSS 6.5)
- CVE-2018-25421MEDIUMOpen STA Manager 2.3 Path Traversal File Download Vulnerability
- CVE-2019-25734MEDIUMContact Form by WD CSRF & Local File Inclusion Vulnerability
- CVE-2019-25740MEDIUMJoomla com_jsjobs Arbitrary File Deletion Vulnerability
- CVE-2022-50953MEDIUMWordPress admin-word-count-column Plugin Local File Read Vulnerability
- CVE-2024-47263MEDIUMSynology Hyper Backup Path Traversal – Admin Privilege Required
- CVE-2024-47273MEDIUMSynology Hyper Backup Path Traversal Vulnerability (4.3 MEDIUM)
- CVE-2025-24268MEDIUMmacOS Path Traversal Vulnerability – Patch Sequoia 15.4