Findings

CVE-2026-3339

The Keep Backup Daily plugin for WordPress is vulnerable to Limited Path Traversal in all versions up to, and including, 2.1.1 via the AJAX action.

Published Mar 21, 2026 · updated Jun 17, 2026

The Keep Backup Daily plugin for WordPress is vulnerable to Limited Path Traversal in all versions up to, and including, 2.1.1 via the AJAX action. This is due to insufficient validation of the parameter, which is only sanitized with - a function that does not strip path traversal sequences. This makes it possible for authenticated attackers, with Administrator-level access and above, to list the contents of arbitrary directories on the server outside of the intended uploads directory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 21, 2026 · NIST NVD

    Detected

    The Keep Backup Daily plugin for WordPress is vulnerable to Limited Path Traversal in all versions up to, and including, 2.1.1 via the AJAX action. This is due to insufficient validation of the parameter, which is only sanitized with - a function that does not strip path traversal sequences. This makes it possible for authenticated attackers, with Administrator-level access and above, to list the

  2. Jun 17, 2026 · NIST NVD

    Updated

    The Keep Backup Daily plugin for WordPress is vulnerable to Limited Path Traversal in all versions up to, and including, 2.1.1 via the AJAX action. This is due to insufficient validation of the parameter, which is only sanitized with - a function that does not strip path traversal sequences. This makes it possible for authenticated attackers, with Administrator-level access and above, to list the

Sources

  • CVE.orgVulnerability recordCVE-2026-3339

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-3339

    The Keep Backup Daily plugin for WordPress is vulnerable to Limited Path Traversal in all versions up to, and including, 2.1.1 via the AJAX action. This is due to insufficient validation of the parameter, which is only sanitized with `sanitize_tex

    nvd.nist.gov

References