CVE-2025-13070: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in CSV to SortTable
The CSV to SortTable WordPress plugin through 4.2 does not validate some shortcode attributes before using them to generate paths passed to include function/s, allowing any authenticated users such as contributor to perform LFI attacks.
AI Analysis
Technical Summary
CVE-2025-13070 is a path traversal vulnerability classified under CWE-22 affecting the CSV to SortTable WordPress plugin through version 4.2. The issue arises because the plugin fails to properly validate certain shortcode attributes before using them to construct file paths passed to PHP include functions. This improper validation allows an authenticated user with contributor-level privileges or higher to manipulate the path parameters, enabling local file inclusion (LFI) attacks. Through LFI, an attacker can read arbitrary files on the server, potentially exposing sensitive configuration files, credentials, or other data. Additionally, depending on the server configuration, this could lead to remote code execution or denial of service by including malicious files or disrupting normal operations. The vulnerability requires authenticated access, which limits the attack surface to users with at least contributor permissions. The CVSS 3.1 base score is 6.6 (medium severity), reflecting network attack vector, high privileges required, no user interaction, and high impact on confidentiality, integrity, and availability. No public exploits or patches are currently available, but the vulnerability is published and should be addressed promptly. The plugin is used in WordPress environments, which are common across many European organizations for content management and web presence.
Potential Impact
For European organizations, this vulnerability poses a significant risk to the confidentiality, integrity, and availability of their WordPress-hosted websites and potentially underlying infrastructure. Attackers with contributor-level access could exploit this flaw to read sensitive files such as configuration files containing database credentials or API keys, leading to further compromise. Integrity could be impacted if attackers manage to include malicious files or disrupt site functionality, potentially damaging reputation and user trust. Availability could be affected if the inclusion of malicious or malformed files causes site crashes or denial of service. Organizations with multi-user WordPress setups, especially those allowing external contributors or less-trusted users to add content, are particularly vulnerable. The risk is heightened for sectors with strict data protection regulations like GDPR, where data leakage could result in regulatory penalties. Since no known exploits are in the wild yet, proactive mitigation is critical to prevent exploitation. The medium severity score suggests the threat is serious but not critical, mainly due to the requirement for authenticated access and some attack complexity.
Mitigation Recommendations
1. Monitor for and apply plugin updates immediately once a patch addressing CVE-2025-13070 is released by the plugin developer. 2. Until a patch is available, restrict contributor and other authenticated user permissions to the minimum necessary, avoiding granting unnecessary access to shortcode editing or plugin configuration. 3. Implement Web Application Firewall (WAF) rules to detect and block path traversal patterns and suspicious include path manipulations in HTTP requests targeting WordPress shortcode parameters. 4. Conduct regular audits of user roles and permissions within WordPress to ensure only trusted users have contributor-level or higher access. 5. Employ file integrity monitoring on WordPress directories to detect unauthorized file changes or inclusions. 6. Use security plugins that can sandbox or restrict plugin behavior, limiting the impact of vulnerabilities. 7. Educate content contributors about security best practices and the risks of unauthorized file access. 8. Consider isolating WordPress instances or running them with least privilege on the server to limit the impact of any successful exploitation.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Sweden
CVE-2025-13070: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in CSV to SortTable
Description
The CSV to SortTable WordPress plugin through 4.2 does not validate some shortcode attributes before using them to generate paths passed to include function/s, allowing any authenticated users such as contributor to perform LFI attacks.
AI-Powered Analysis
Technical Analysis
CVE-2025-13070 is a path traversal vulnerability classified under CWE-22 affecting the CSV to SortTable WordPress plugin through version 4.2. The issue arises because the plugin fails to properly validate certain shortcode attributes before using them to construct file paths passed to PHP include functions. This improper validation allows an authenticated user with contributor-level privileges or higher to manipulate the path parameters, enabling local file inclusion (LFI) attacks. Through LFI, an attacker can read arbitrary files on the server, potentially exposing sensitive configuration files, credentials, or other data. Additionally, depending on the server configuration, this could lead to remote code execution or denial of service by including malicious files or disrupting normal operations. The vulnerability requires authenticated access, which limits the attack surface to users with at least contributor permissions. The CVSS 3.1 base score is 6.6 (medium severity), reflecting network attack vector, high privileges required, no user interaction, and high impact on confidentiality, integrity, and availability. No public exploits or patches are currently available, but the vulnerability is published and should be addressed promptly. The plugin is used in WordPress environments, which are common across many European organizations for content management and web presence.
Potential Impact
For European organizations, this vulnerability poses a significant risk to the confidentiality, integrity, and availability of their WordPress-hosted websites and potentially underlying infrastructure. Attackers with contributor-level access could exploit this flaw to read sensitive files such as configuration files containing database credentials or API keys, leading to further compromise. Integrity could be impacted if attackers manage to include malicious files or disrupt site functionality, potentially damaging reputation and user trust. Availability could be affected if the inclusion of malicious or malformed files causes site crashes or denial of service. Organizations with multi-user WordPress setups, especially those allowing external contributors or less-trusted users to add content, are particularly vulnerable. The risk is heightened for sectors with strict data protection regulations like GDPR, where data leakage could result in regulatory penalties. Since no known exploits are in the wild yet, proactive mitigation is critical to prevent exploitation. The medium severity score suggests the threat is serious but not critical, mainly due to the requirement for authenticated access and some attack complexity.
Mitigation Recommendations
1. Monitor for and apply plugin updates immediately once a patch addressing CVE-2025-13070 is released by the plugin developer. 2. Until a patch is available, restrict contributor and other authenticated user permissions to the minimum necessary, avoiding granting unnecessary access to shortcode editing or plugin configuration. 3. Implement Web Application Firewall (WAF) rules to detect and block path traversal patterns and suspicious include path manipulations in HTTP requests targeting WordPress shortcode parameters. 4. Conduct regular audits of user roles and permissions within WordPress to ensure only trusted users have contributor-level or higher access. 5. Employ file integrity monitoring on WordPress directories to detect unauthorized file changes or inclusions. 6. Use security plugins that can sandbox or restrict plugin behavior, limiting the impact of vulnerabilities. 7. Educate content contributors about security best practices and the risks of unauthorized file access. 8. Consider isolating WordPress instances or running them with least privilege on the server to limit the impact of any successful exploitation.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- WPScan
- Date Reserved
- 2025-11-12T14:25:22.022Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 6937bd663ce8502056bafcc2
Added to database: 12/9/2025, 6:10:46 AM
Last enriched: 1/9/2026, 8:52:11 PM
Last updated: 2/4/2026, 7:04:11 PM
Views: 85
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.
Related Threats
CVE-2026-0536: CWE-787 Out-of-bounds Write in Autodesk 3ds Max
HighCVE-2024-42642: n/a
CriticalCVE-2026-25532: CWE-191: Integer Underflow (Wrap or Wraparound) in espressif esp-idf
MediumCVE-2026-25508: CWE-125: Out-of-bounds Read in espressif esp-idf
MediumCVE-2026-25507: CWE-416: Use After Free in espressif esp-idf
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.