Delete Comments By Status: Filesystem traversal
Delete Comments By Status is affected by filesystem traversal. Exposure depends on how the affected operation is made reachable by the site. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.
- Component
- Delete Comments By Status
- Plugin slug
delete-comments-by-status- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Mar 03, 2025
- Weakness
- CWE-23 — Relative Path Traversal
This CVE was published Mar 03, 2025 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Delete Comments By Status to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
Relative Path Traversal vulnerability in Shah Alom Delete Comments By Status delete-comments-by-status allows Path Traversal.This issue affects Delete Comments By Status: from n/a through <= 2.1.1.
CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H